Central plant optimization planning tool with advanced user interface

ABSTRACT

A system for operating or designing building equipment is configured to provide a user interface comprising a workspace with selectable symbols representing multiple devices of building equipment, evaluate a user input defining a connection between at least two of the selectable symbols on the workspace according to a set of rules to determine whether the connection is valid or invalid, prevent the user from making the connection in response to determining that the connection is invalid, generate a valid model of a system comprising the multiple devices of building equipment in response to determining that the connection is valid, execute a model-based control process or simulation using the valid model to generate control decisions or design decisions for the multiple devices of building equipment, and operate or design the multiple devices of building equipment in accordance with the control decisions or the design decisions.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 16/370,632, filed Mar. 29, 2019, which claims the benefit of and priority to Indian Provisional Patent Application No. 201821012277 filed Mar. 31, 2018, both of which are incorporated by reference herein in their entireties.

BACKGROUND

The present disclosure relates generally to a central plant or central energy facility configured to serve the energy loads of a building or campus. The present disclosure relates more particularly to a central plant with an asset allocator configured to determine an optimal distribution of the energy loads across various subplants of the central plant.

A central plant typically include multiple subplants configured to serve different types of energy loads. For example, a central plant may include a chiller subplant configured to serve cooling loads, a heater subplant configured to serve heating loads, and/or an electricity subplant configured to serve electric loads. A central plant purchases resources from utilities to run the subplants to meet the loads.

Some central plants include energy storage. Energy storage may be a tank of water that stores hot water for campus heating, an ice tank for campus cooling, and/or battery storage. In the presence of real-time pricing from utilities, it may be advantageous to manipulate the time that a certain resource or energy type is consumed. Instead of producing the resource exactly when it is required by the load, it can be optimal to produce that resource at a time when the production cost is low, store it, and then use it when the resource needed to produce that type of energy is more expensive.

It can be difficult and challenging to optimally allocate the energy loads across the assets of the central plant. Further, it can be difficult to determine how to design a central plant in an efficient manner. It is generally desirable to have computerized systems that can simplify the central plant design process.

SUMMARY

One implementation of the present disclosure is a system including one or more computer-readable storage media having instructions stored thereon that, when executed by one or more processors, cause the one or more processors to provide a user interface to a user via a computing device, the user interface including a symbol palette with selectable symbols representing resource suppliers, subplants, energy loads, and resource storage devices associated with a central plant; receive a first input from the user via the user interface, the first input including placement of the symbols from the symbol palette on a workspace of the user interface, the symbols placed on the workspace including at least a resource supplier, a subplant, and an energy load; receive a second input form the user via the user interface, the second input including a connection between two of the symbols on the workspace; evaluate the second input according to a set of rules to determine that the connection is invalid; prevent the user from making the connection; receive a third user input from the user via the user interface, the third user input including additional connections between the symbols on the workspace, the third user input completing a valid model of the central plant according to the set of rules; and simulate operation of the central plant in accordance with the valid model to provide the user with insight regarding how to optimize the central plant.

In some embodiments, the resource suppliers include an electricity supplier, a water supplier, a natural gas supplier, and a steam supplier; the subplants include a chiller plant, a boiler plant, a tower plant, and a heat recovery chiller plant; the energy loads include a chilled water load and a hot water load; and the resource devices include a thermal storage tank.

In some embodiments, the set of rules defines valid relationships between the resource suppliers and the subplants.

In some embodiments, the set of rules defines valid relationships between the subplants and the energy loads.

In some embodiments, the set of rules defines valid relationships between the subplants and the resource storage devices.

In some embodiments, the instructions cause the one or more processors to receive a fourth user input via the user interface, the fourth user input including equipment contained within the subplant.

In some embodiments, the set of rules defines equipment that is required to be contained within one or more of the subplants.

In some embodiments, the instructions cause the one or more processors to display the additional connections between the symbols on the workspace as colored objects, and a color of the colored objects corresponds to a resource type.

In some embodiments, the instructions cause the one or more processors to present a list of missing connections between the symbols on the workspace to the user via the user interface in accordance with the set of rules.

In some embodiments, the computing device is a smartphone, a tablet, a personal computer, or a laptop.

Another implementation of the present disclosure is a method for providing a user with insight regarding how to optimize a central plant. The method includes providing a user interface to the user via a computing device, the user interface including a symbol palette with selectable symbols representing resource suppliers, subplants, energy loads, and resource storage devices associated with the central plant; receiving a first input from the user via the user interface, the first input including placement of the symbols from the symbol palette on a workspace of the user interface, the symbols placed on the workspace including at least a resource supplier, a subplant, and an energy load; receiving a second input form the user via the user interface, the second input including a connection between two of the symbols on the workspace; evaluating the second input according to a set of rules to determine that the connection is improper; preventing the user from making the connection; receiving a third user input from the user via the user interface, the third user input including additional connections between the symbols on the workspace, the third user input completing a valid model of the central plant according to the set of rules; and simulating operation of the central plant in accordance with the valid model to provide the user with the insight regarding how to optimize the central plant.

In some embodiments, the resource suppliers include an electricity supplier, a water supplier, a natural gas supplier, and a steam supplier; the subplants include a chiller plant, a boiler plant, a tower plant, and a heat recovery chiller plant; the energy loads include a chilled water load and a hot water load; and the resource devices include a thermal storage tank.

In some embodiments, the set of rules defines valid relationships between the resource suppliers and the subplants.

In some embodiments, the set of rules defines valid relationships between the subplants and the energy loads.

In some embodiments, the set of rules defines valid relationships between the subplants and the resource storage devices.

In some embodiments, the method further includes receiving a fourth input from the user via the user interface, the fourth input including equipment contained within the subplant.

In some embodiments, the set of rules defines equipment that is required to be contained within one or more of the subplants.

In some embodiments, the method further includes displaying the additional connections between the symbols on the workspace as colored objects, and a color of the colored objects corresponds to a resource type.

In some embodiments, the method further includes presenting a list of missing connections between the symbols on the workspace to the user via the user interface in accordance with the set of rules.

In some embodiments, the computing device is a smartphone, a tablet, a personal computer, or a laptop.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a drawing of a building equipped with a HVAC system, according to some embodiments.

FIG. 2 is a block diagram of a central plant which can be used to serve the energy loads of the building of FIG. 1, according to some embodiments.

FIG. 3 is a block diagram of an airside system which can be implemented in the building of FIG. 1, according to some embodiments.

FIG. 4 is a block diagram of an asset allocation system including sources, subplants, storage, sinks, and an asset allocator configured to optimize the allocation of these assets, according to some embodiments.

FIG. 5A is a plant resource diagram illustrating the elements of a central plant and the connections between such elements, according to some embodiments.

FIG. 5B is another plant resource diagram illustrating the elements of a central plant and the connections between such elements, according to some embodiments.

FIG. 6 is a block diagram of a central plant controller in which the asset allocator of FIG. 4 can be implemented, according to some embodiments.

FIG. 7 is a block diagram of a planning tool in which the asset allocator of FIG. 4 can be implemented, according to some embodiments.

FIG. 8 is a flow diagram illustrating an optimization process which can be performed by the planning tool of FIG. 7, according to some embodiments.

FIG. 9 is a block diagram illustrating the asset allocator of FIG. 4 in greater detail, according to some embodiments.

FIG. 10 is a drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 11 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 12 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 13 another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 14 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 15 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 16 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 17 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 18 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 19 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 20 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 21 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 22 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 23 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 24 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 25 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 26 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 27 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 28 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 29 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 30 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 31 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 32 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 33 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 34 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 35 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 36 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 37 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 38 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 39 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 40 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 41 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 42 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 43 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIG. 44 is another drawing of a user interface associated with the planning tool of FIG. 7, according to some embodiments.

FIGS. 45A-45B are a table showing an example set of rules associated with the planning tool of FIG. 7, according to some embodiments.

DETAILED DESCRIPTION Overview

Referring generally to the FIGURES, a planning tool that can be used to facilitate the design of a central plant is shown, according to various embodiments. The planning tool includes an intuitive user interface designed to assist the user in properly configuring a central plant model. The interface includes graphics, symbols, colors, and visual feedback. The planning tool may include a set of rules associated with different types of resources, subplants, storage, and sinks that can be included in the central plant model. The rules may define required and optional inputs and outputs, for example. The improved user interface of the planning tool facilitates efficient and feasible central plant design.

Building and HVAC System

Referring now to FIG. 1, a perspective view of a building 10 is shown. Building 10 can be served by a building management system (BMS). A BMS is, in general, a system of devices configured to control, monitor, and manage equipment in or around a building or building area. A BMS can include, for example, a HVAC system, a security system, a lighting system, a fire alerting system, any other system that is capable of managing building functions or devices, or any combination thereof. An example of a BMS which can be used to monitor and control building 10 is described in U.S. patent application Ser. No. 14/717,593 filed May 20, 2015, the entire disclosure of which is incorporated by reference herein.

The BMS that serves building 10 may include a HVAC system 100. HVAC system 100 can include a plurality of HVAC devices (e.g., heaters, chillers, air handling units, pumps, fans, thermal energy storage, etc.) configured to provide heating, cooling, ventilation, or other services for building 10. For example, HVAC system 100 is shown to include a waterside system 120 and an airside system 130. Waterside system 120 may provide a heated or chilled fluid to an air handling unit of airside system 130. Airside system 130 may use the heated or chilled fluid to heat or cool an airflow provided to building 10. In some embodiments, waterside system 120 can be replaced with or supplemented by a central plant or central energy facility (described in greater detail with reference to FIG. 2). An example of an airside system which can be used in HVAC system 100 is described in greater detail with reference to FIG. 3.

HVAC system 100 is shown to include a chiller 102, a boiler 104, and a rooftop air handling unit (AHU) 106. Waterside system 120 may use boiler 104 and chiller 102 to heat or cool a working fluid (e.g., water, glycol, etc.) and may circulate the working fluid to AHU 106. In various embodiments, the HVAC devices of waterside system 120 can be located in or around building 10 (as shown in FIG. 1) or at an offsite location such as a central plant (e.g., a chiller plant, a steam plant, a heat plant, etc.). The working fluid can be heated in boiler 104 or cooled in chiller 102, depending on whether heating or cooling is required in building 10. Boiler 104 may add heat to the circulated fluid, for example, by burning a combustible material (e.g., natural gas) or using an electric heating element. Chiller 102 may place the circulated fluid in a heat exchange relationship with another fluid (e.g., a refrigerant) in a heat exchanger (e.g., an evaporator) to absorb heat from the circulated fluid. The working fluid from chiller 102 and/or boiler 104 can be transported to AHU 106 via piping 108.

AHU 106 may place the working fluid in a heat exchange relationship with an airflow passing through AHU 106 (e.g., via one or more stages of cooling coils and/or heating coils). The airflow can be, for example, outside air, return air from within building 10, or a combination of both. AHU 106 may transfer heat between the airflow and the working fluid to provide heating or cooling for the airflow. For example, AHU 106 can include one or more fans or blowers configured to pass the airflow over or through a heat exchanger containing the working fluid. The working fluid may then return to chiller 102 or boiler 104 via piping 110.

Airside system 130 may deliver the airflow supplied by AHU 106 (i.e., the supply airflow) to building 10 via air supply ducts 112 and may provide return air from building 10 to AHU 106 via air return ducts 114. In some embodiments, airside system 130 includes multiple variable air volume (VAV) units 116. For example, airside system 130 is shown to include a separate VAV unit 116 on each floor or zone of building 10. VAV units 116 can include dampers or other flow control elements that can be operated to control an amount of the supply airflow provided to individual zones of building 10. In other embodiments, airside system 130 delivers the supply airflow into one or more zones of building 10 (e.g., via supply ducts 112) without using intermediate VAV units 116 or other flow control elements. AHU 106 can include various sensors (e.g., temperature sensors, pressure sensors, etc.) configured to measure attributes of the supply airflow. AHU 106 may receive input from sensors located within AHU 106 and/or within the building zone and may adjust the flow rate, temperature, or other attributes of the supply airflow through AHU 106 to achieve setpoint conditions for the building zone.

Central Plant

Referring now to FIG. 2, a block diagram of a central plant 200 is shown, according to some embodiments. In various embodiments, central plant 200 can supplement or replace waterside system 120 in HVAC system 100 or can be implemented separate from HVAC system 100. When implemented in HVAC system 100, central plant 200 can include a subset of the HVAC devices in HVAC system 100 (e.g., boiler 104, chiller 102, pumps, valves, etc.) and may operate to supply a heated or chilled fluid to AHU 106. The HVAC devices of central plant 200 can be located within building 10 (e.g., as components of waterside system 120) or at an offsite location such as a central energy facility that serves multiple buildings.

Central plant 200 is shown to include a plurality of subplants 202-208. Subplants 202-208 can be configured to convert energy or resource types (e.g., water, natural gas, electricity, etc.). For example, subplants 202-208 are shown to include a heater subplant 202, a heat recovery chiller subplant 204, a chiller subplant 206, and a cooling tower subplant 208. In some embodiments, subplants 202-208 consume resources purchased from utilities to serve the energy loads (e.g., hot water, cold water, electricity, etc.) of a building or campus. For example, heater subplant 202 can be configured to heat water in a hot water loop 214 that circulates the hot water between heater subplant 202 and building 10. Similarly, chiller subplant 206 can be configured to chill water in a cold water loop 216 that circulates the cold water between chiller subplant 206 building 10.

Heat recovery chiller subplant 204 can be configured to transfer heat from cold water loop 216 to hot water loop 214 to provide additional heating for the hot water and additional cooling for the cold water. Condenser water loop 218 may absorb heat from the cold water in chiller subplant 206 and reject the absorbed heat in cooling tower subplant 208 or transfer the absorbed heat to hot water loop 214. In various embodiments, central plant 200 can include an electricity subplant (e.g., one or more electric generators) configured to generate electricity or any other type of subplant configured to convert energy or resource types.

Hot water loop 214 and cold water loop 216 may deliver the heated and/or chilled water to air handlers located on the rooftop of building 10 (e.g., AHU 106) or to individual floors or zones of building 10 (e.g., VAV units 116). The air handlers push air past heat exchangers (e.g., heating coils or cooling coils) through which the water flows to provide heating or cooling for the air. The heated or cooled air can be delivered to individual zones of building 10 to serve thermal energy loads of building 10. The water then returns to subplants 202-208 to receive further heating or cooling.

Although subplants 202-208 are shown and described as heating and cooling water for circulation to a building, it is understood that any other type of working fluid (e.g., glycol, CO₂, etc.) can be used in place of or in addition to water to serve thermal energy loads. In other embodiments, subplants 202-208 may provide heating and/or cooling directly to the building or campus without requiring an intermediate heat transfer fluid. These and other variations to central plant 200 are within the teachings of the present disclosure.

Each of subplants 202-208 can include a variety of equipment configured to facilitate the functions of the subplant. For example, heater subplant 202 is shown to include a plurality of heating elements 220 (e.g., boilers, electric heaters, etc.) configured to add heat to the hot water in hot water loop 214. Heater subplant 202 is also shown to include several pumps 222 and 224 configured to circulate the hot water in hot water loop 214 and to control the flow rate of the hot water through individual heating elements 220. Chiller subplant 206 is shown to include a plurality of chillers 232 configured to remove heat from the cold water in cold water loop 216. Chiller subplant 206 is also shown to include several pumps 234 and 236 configured to circulate the cold water in cold water loop 216 and to control the flow rate of the cold water through individual chillers 232.

Heat recovery chiller subplant 204 is shown to include a plurality of heat recovery heat exchangers 226 (e.g., refrigeration circuits) configured to transfer heat from cold water loop 216 to hot water loop 214. Heat recovery chiller subplant 204 is also shown to include several pumps 228 and 230 configured to circulate the hot water and/or cold water through heat recovery heat exchangers 226 and to control the flow rate of the water through individual heat recovery heat exchangers 226. Cooling tower subplant 208 is shown to include a plurality of cooling towers 238 configured to remove heat from the condenser water in condenser water loop 218. Cooling tower subplant 208 is also shown to include several pumps 240 configured to circulate the condenser water in condenser water loop 218 and to control the flow rate of the condenser water through individual cooling towers 238.

In some embodiments, one or more of the pumps in central plant 200 (e.g., pumps 222, 224, 228, 230, 234, 236, and/or 240) or pipelines in central plant 200 include an isolation valve associated therewith. Isolation valves can be integrated with the pumps or positioned upstream or downstream of the pumps to control the fluid flows in central plant 200. In various embodiments, central plant 200 can include more, fewer, or different types of devices and/or subplants based on the particular configuration of central plant 200 and the types of loads served by central plant 200.

Still referring to FIG. 2, central plant 200 is shown to include hot thermal energy storage (TES) 210 and cold thermal energy storage (TES) 212. Hot TES 210 and cold TES 212 can be configured to store hot and cold thermal energy for subsequent use. For example, hot TES 210 can include one or more hot water storage tanks 242 configured to store the hot water generated by heater subplant 202 or heat recovery chiller subplant 204. Hot TES 210 may also include one or more pumps or valves configured to control the flow rate of the hot water into or out of hot TES tank 242.

Similarly, cold TES 212 can include one or more cold water storage tanks 244 configured to store the cold water generated by chiller subplant 206 or heat recovery chiller subplant 204. Cold TES 212 may also include one or more pumps or valves configured to control the flow rate of the cold water into or out of cold TES tanks 244. In some embodiments, central plant 200 includes electrical energy storage (e.g., one or more batteries) or any other type of device configured to store resources. The stored resources can be purchased from utilities, generated by central plant 200, or otherwise obtained from any source.

Airside System

Referring now to FIG. 3, a block diagram of an airside system 300 is shown, according to some embodiments. In various embodiments, airside system 300 may supplement or replace airside system 130 in HVAC system 100 or can be implemented separate from HVAC system 100. When implemented in HVAC system 100, airside system 300 can include a subset of the HVAC devices in HVAC system 100 (e.g., AHU 106, VAV units 116, ducts 112-114, fans, dampers, etc.) and can be located in or around building 10. Airside system 300 may operate to heat or cool an airflow provided to building 10 using a heated or chilled fluid provided by central plant 200.

Airside system 300 is shown to include an economizer-type air handling unit (AHU) 302. Economizer-type AHUs vary the amount of outside air and return air used by the air handling unit for heating or cooling. For example, AHU 302 may receive return air 304 from building zone 306 via return air duct 308 and may deliver supply air 310 to building zone 306 via supply air duct 312. In some embodiments, AHU 302 is a rooftop unit located on the roof of building 10 (e.g., AHU 106 as shown in FIG. 1) or otherwise positioned to receive both return air 304 and outside air 314. AHU 302 can be configured to operate exhaust air damper 316, mixing damper 318, and outside air damper 320 to control an amount of outside air 314 and return air 304 that combine to form supply air 310. Any return air 304 that does not pass through mixing damper 318 can be exhausted from AHU 302 through exhaust damper 316 as exhaust air 322.

Each of dampers 316-320 can be operated by an actuator. For example, exhaust air damper 316 can be operated by actuator 324, mixing damper 318 can be operated by actuator 326, and outside air damper 320 can be operated by actuator 328. Actuators 324-328 may communicate with an AHU controller 330 via a communications link 332. Actuators 324-328 may receive control signals from AHU controller 330 and may provide feedback signals to AHU controller 330. Feedback signals can include, for example, an indication of a current actuator or damper position, an amount of torque or force exerted by the actuator, diagnostic information (e.g., results of diagnostic tests performed by actuators 324-328), status information, commissioning information, configuration settings, calibration data, and/or other types of information or data that can be collected, stored, or used by actuators 324-328. AHU controller 330 can be an economizer controller configured to use one or more control algorithms (e.g., state-based algorithms, extremum seeking control (ESC) algorithms, proportional-integral (PI) control algorithms, proportional-integral-derivative (PID) control algorithms, model predictive control (MPC) algorithms, feedback control algorithms, etc.) to control actuators 324-328.

Still referring to FIG. 3, AHU 302 is shown to include a cooling coil 334, a heating coil 336, and a fan 338 positioned within supply air duct 312. Fan 338 can be configured to force supply air 310 through cooling coil 334 and/or heating coil 336 and provide supply air 310 to building zone 306. AHU controller 330 may communicate with fan 338 via communications link 340 to control a flow rate of supply air 310. In some embodiments, AHU controller 330 controls an amount of heating or cooling applied to supply air 310 by modulating a speed of fan 338.

Cooling coil 334 may receive a chilled fluid from central plant 200 (e.g., from cold water loop 216) via piping 342 and may return the chilled fluid to central plant 200 via piping 344. Valve 346 can be positioned along piping 342 or piping 344 to control a flow rate of the chilled fluid through cooling coil 334. In some embodiments, cooling coil 334 includes multiple stages of cooling coils that can be independently activated and deactivated (e.g., by AHU controller 330, by BMS controller 366, etc.) to modulate an amount of cooling applied to supply air 310.

Heating coil 336 may receive a heated fluid from central plant 200 (e.g., from hot water loop 214) via piping 348 and may return the heated fluid to central plant 200 via piping 350. Valve 352 can be positioned along piping 348 or piping 350 to control a flow rate of the heated fluid through heating coil 336. In some embodiments, heating coil 336 includes multiple stages of heating coils that can be independently activated and deactivated (e.g., by AHU controller 330, by BMS controller 366, etc.) to modulate an amount of heating applied to supply air 310.

Each of valves 346 and 352 can be controlled by an actuator. For example, valve 346 can be controlled by actuator 354 and valve 352 can be controlled by actuator 356. Actuators 354-356 may communicate with AHU controller 330 via communications links 358-360. Actuators 354-356 may receive control signals from AHU controller 330 and may provide feedback signals to controller 330. In some embodiments, AHU controller 330 receives a measurement of the supply air temperature from a temperature sensor 362 positioned in supply air duct 312 (e.g., downstream of cooling coil 334 and/or heating coil 336). AHU controller 330 may also receive a measurement of the temperature of building zone 306 from a temperature sensor 364 located in building zone 306.

In some embodiments, AHU controller 330 operates valves 346 and 352 via actuators 354-356 to modulate an amount of heating or cooling provided to supply air 310 (e.g., to achieve a setpoint temperature for supply air 310 or to maintain the temperature of supply air 310 within a setpoint temperature range). The positions of valves 346 and 352 affect the amount of heating or cooling provided to supply air 310 by cooling coil 334 or heating coil 336 and may correlate with the amount of energy consumed to achieve a desired supply air temperature. AHU 330 may control the temperature of supply air 310 and/or building zone 306 by activating or deactivating coils 334-336, adjusting a speed of fan 338, or a combination of both.

Still referring to FIG. 3, airside system 300 is shown to include a building management system (BMS) controller 366 and a client device 368. BMS controller 366 can include one or more computer systems (e.g., servers, supervisory controllers, subsystem controllers, etc.) that serve as system level controllers, application or data servers, head nodes, or master controllers for airside system 300, central plant 200, HVAC system 100, and/or other controllable systems that serve building 10. BMS controller 366 may communicate with multiple downstream building systems or subsystems (e.g., HVAC system 100, a security system, a lighting system, central plant 200, etc.) via a communications link 370 according to like or disparate protocols (e.g., LON, BACnet, etc.). In various embodiments, AHU controller 330 and BMS controller 366 can be separate (as shown in FIG. 3) or integrated. In an integrated implementation, AHU controller 330 can be a software module configured for execution by a processor of BMS controller 366.

In some embodiments, AHU controller 330 receives information from BMS controller 366 (e.g., commands, setpoints, operating boundaries, etc.) and provides information to BMS controller 366 (e.g., temperature measurements, valve or actuator positions, operating statuses, diagnostics, etc.). For example, AHU controller 330 may provide BMS controller 366 with temperature measurements from temperature sensors 362-364, equipment on/off states, equipment operating capacities, and/or any other information that can be used by BMS controller 366 to monitor or control a variable state or condition within building zone 306.

Client device 368 can include one or more human-machine interfaces or client interfaces (e.g., graphical user interfaces, reporting interfaces, text-based computer interfaces, client-facing web services, web servers that provide pages to web clients, etc.) for controlling, viewing, or otherwise interacting with HVAC system 100, its subsystems, and/or devices. Client device 368 can be a computer workstation, a client terminal, a remote or local interface, or any other type of user interface device. Client device 368 can be a stationary terminal or a mobile device. For example, client device 368 can be a desktop computer, a computer server with a user interface, a laptop computer, a tablet, a smartphone, a PDA, or any other type of mobile or non-mobile device. Client device 368 may communicate with BMS controller 366 and/or AHU controller 330 via communications link 372.

Asset Allocation System

Referring now to FIG. 4, a block diagram of an asset allocation system 400 is shown, according to an exemplary embodiment. Asset allocation system 400 can be configured to manage energy assets such as central plant equipment, battery storage, and other types of equipment configured to serve the energy loads of a building. Asset allocation system 400 can determine an optimal distribution of heating, cooling, electricity, and energy loads across different subplants (i.e., equipment groups) capable of producing that type of energy. In some embodiments, asset allocation system 400 is implemented as a component of central plant 200 and interacts with the equipment of central plant 200 in an online operational environment (e.g., performing real-time control of the central plant equipment). In other embodiments, asset allocation system 400 can be implemented as a component of a planning tool (described with reference to FIGS. 7-8) and can be configured to simulate the operation of a central plant over a predetermined time period for planning, budgeting, and/or design considerations.

Asset allocation system 400 is shown to include sources 410, subplants 420, storage 430, and sinks 440. These four categories of objects define the assets of a central plant and their interaction with the outside world. Sources 410 may include commodity markets or other suppliers from which resources such as electricity, water, natural gas, and other resources can be purchased or obtained. Sources 410 may provide resources that can be used by asset allocation system 400 to satisfy the demand of a building or campus. For example, sources 410 are shown to include an electric utility 411, a water utility 412, a natural gas utility 413, a photovoltaic (PV) field (e.g., a collection of solar panels), an energy market 415, and source M 416, where M is the total number of sources 410. Resources purchased from sources 410 can be used by subplants 420 to produce generated resources (e.g., hot water, cold water, electricity, steam, etc.), stored in storage 430 for later use, or provided directly to sinks 440.

Subplants 420 are the main assets of a central plant. Subplants 420 are shown to include a heater subplant 421, a chiller subplant 422, a heat recovery chiller subplant 423, a steam subplant 424, an electricity subplant 425, and subplant N, where N is the total number of subplants 420. In some embodiments, subplants 420 include some or all of the subplants of central plant 200, as described with reference to FIG. 2. For example, subplants 420 can include heater subplant 202, heat recovery chiller subplant 204, chiller subplant 206, and/or cooling tower subplant 208.

Subplants 420 can be configured to convert resource types, making it possible to balance requested loads from the building or campus using resources purchased from sources 410. For example, heater subplant 421 may be configured to generate hot thermal energy (e.g., hot water) by heating water using electricity or natural gas. Chiller subplant 422 may be configured to generate cold thermal energy (e.g., cold water) by chilling water using electricity. Heat recovery chiller subplant 423 may be configured to generate hot thermal energy and cold thermal energy by removing heat from one water supply and adding the heat to another water supply. Steam subplant 424 may be configured to generate steam by boiling water using electricity or natural gas. Electricity subplant 425 may be configured to generate electricity using mechanical generators (e.g., a steam turbine, a gas-powered generator, etc.) or other types of electricity-generating equipment (e.g., photovoltaic equipment, hydroelectric equipment, etc.).

The input resources used by subplants 420 may be provided by sources 410, retrieved from storage 430, and/or generated by other subplants 420. For example, steam subplant 424 may produce steam as an output resource. Electricity subplant 425 may include a steam turbine that uses the steam generated by steam subplant 424 as an input resource to generate electricity. The output resources produced by subplants 420 may be stored in storage 430, provided to sinks 440, and/or used by other subplants 420. For example, the electricity generated by electricity subplant 425 may be stored in electrical energy storage 433, used by chiller subplant 422 to generate cold thermal energy, used to satisfy the electric load 445 of a building, or sold to resource purchasers 441.

Storage 430 can be configured to store energy or other types of resources for later use. Each type of storage within storage 430 may be configured to store a different type of resource. For example, storage 430 is shown to include hot thermal energy storage 431 (e.g., one or more hot water storage tanks), cold thermal energy storage 432 (e.g., one or more cold thermal energy storage tanks), electrical energy storage 433 (e.g., one or more batteries), and resource type P storage 434, where P is the total number of storage 430. In some embodiments, storage 430 include some or all of the storage of central plant 200, as described with reference to FIG. 2. In some embodiments, storage 430 includes the heat capacity of the building served by the central plant. The resources stored in storage 430 may be purchased directly from sources or generated by subplants 420.

In some embodiments, storage 430 is used by asset allocation system 400 to take advantage of price-based demand response (PBDR) programs. PBDR programs encourage consumers to reduce consumption when generation, transmission, and distribution costs are high. PBDR programs are typically implemented (e.g., by sources 410) in the form of energy prices that vary as a function of time. For example, some utilities may increase the price per unit of electricity during peak usage hours to encourage customers to reduce electricity consumption during peak times. Some utilities also charge consumers a separate demand charge based on the maximum rate of electricity consumption at any time during a predetermined demand charge period.

Advantageously, storing energy and other types of resources in storage 430 allows for the resources to be purchased at times when the resources are relatively less expensive (e.g., during non-peak electricity hours) and stored for use at times when the resources are relatively more expensive (e.g., during peak electricity hours). Storing resources in storage 430 also allows the resource demand of the building or campus to be shifted in time. For example, resources can be purchased from sources 410 at times when the demand for heating or cooling is low and immediately converted into hot or cold thermal energy by subplants 420. The thermal energy can be stored in storage 430 and retrieved at times when the demand for heating or cooling is high. This allows asset allocation system 400 to smooth the resource demand of the building or campus and reduces the maximum required capacity of subplants 420. Smoothing the demand also asset allocation system 400 to reduce the peak electricity consumption, which results in a lower demand charge.

In some embodiments, storage 430 is used by asset allocation system 400 to take advantage of incentive-based demand response (IBDR) programs. IBDR programs provide incentives to customers who have the capability to store energy, generate energy, or curtail energy usage upon request. Incentives are typically provided in the form of monetary revenue paid by sources 410 or by an independent service operator (ISO). IBDR programs supplement traditional utility-owned generation, transmission, and distribution assets with additional options for modifying demand load curves. For example, stored energy can be sold to resource purchasers 441 or an energy grid 442 to supplement the energy generated by sources 410. In some instances, incentives for participating in an IBDR program vary based on how quickly a system can respond to a request to change power output/consumption. Faster responses may be compensated at a higher level. Advantageously, electrical energy storage 433 allows system 400 to quickly respond to a request for electric power by rapidly discharging stored electrical energy to energy grid 442.

Sinks 440 may include the requested loads of a building or campus as well as other types of resource consumers. For example, sinks 440 are shown to include resource purchasers 441, an energy grid 442, a hot water load 443, a cold water load 444, an electric load 445, and sink Q, where Q is the total number of sinks 440. A building may consume various resources including, for example, hot thermal energy (e.g., hot water), cold thermal energy (e.g., cold water), and/or electrical energy. In some embodiments, the resources are consumed by equipment or subsystems within the building (e.g., HVAC equipment, lighting, computers and other electronics, etc.). The consumption of each sink 440 over the optimization period can be supplied as an input to asset allocation system 400 or predicted by asset allocation system 400. Sinks 440 can receive resources directly from sources 410, from subplants 420, and/or from storage 430.

Still referring to FIG. 4, asset allocation system 400 is shown to include an asset allocator 402. Asset allocator 402 may be configured to control the distribution, production, storage, and usage of resources in asset allocation system 400. In some embodiments, asset allocator 402 performs an optimization process determine an optimal set of control decisions for each time step within an optimization period. The control decisions may include, for example, an optimal amount of each resource to purchase from sources 410, an optimal amount of each resource to produce or convert using subplants 420, an optimal amount of each resource to store or remove from storage 430, an optimal amount of each resource to sell to resources purchasers 441 or energy grid 440, and/or an optimal amount of each resource to provide to other sinks 440. In some embodiments, the control decisions include an optimal amount of each input resource and output resource for each of subplants 420.

In some embodiments, asset allocator 402 is configured to optimally dispatch all campus energy assets in order to meet the requested heating, cooling, and electrical loads of the campus for each time step within an optimization horizon or optimization period of duration h. Instead of focusing on only the typical HVAC energy loads, the concept is extended to the concept of resource. Throughout this disclosure, the term “resource” is used to describe any type of commodity purchased from sources 410, used or produced by subplants 420, stored or discharged by storage 430, or consumed by sinks 440. For example, water may be considered a resource that is consumed by chillers, heaters, or cooling towers during operation. This general concept of a resource can be extended to chemical processing plants where one of the resources is the product that is being produced by the chemical processing plat.

Asset allocator 402 can be configured to operate the equipment of asset allocation system 400 to ensure that a resource balance is maintained at each time step of the optimization period. This resource balance is shown in the following equation:

Σx _(time)=0 ∀ resources,∀time∈horizon

where the sum is taken over all producers and consumers of a given resource (i.e., all of sources 410, subplants 420, storage 430, and sinks 440) and time is the time index. Each time element represents a period of time during which the resource productions, requests, purchases, etc. are assumed constant. Asset allocator 402 may ensure that this equation is satisfied for all resources regardless of whether that resource is required by the building or campus. For example, some of the resources produced by subplants 420 may be intermediate resources that function only as inputs to other subplants 420.

In some embodiments, the resources balanced by asset allocator 402 include multiple resources of the same type (e.g., multiple chilled water resources, multiple electricity resources, etc.). Defining multiple resources of the same type may allow asset allocator 402 to satisfy the resource balance given the physical constraints and connections of the central plant equipment. For example, suppose a central plant has multiple chillers and multiple cold water storage tanks, with each chiller physically connected to a different cold water storage tank (i.e., chiller A is connected to cold water storage tank A, chiller B is connected to cold water storage tank B, etc.). Given that only one chiller can supply cold water to each cold water storage tank, a different cold water resource can be defined for the output of each chiller. This allows asset allocator 402 to ensure that the resource balance is satisfied for each cold water resource without attempting to allocate resources in a way that is physically impossible (e.g., storing the output of chiller A in cold water storage tank B, etc.).

Asset allocator 402 may be configured to minimize the economic cost (or maximize the economic value) of operating asset allocation system 400 over the duration of the optimization period. The economic cost may be defined by a cost function J(x) that expresses economic cost as a function of the control decisions made by asset allocator 402. The cost function J(x) may account for the cost of resources purchased from sources 410, as well as the revenue generated by selling resources to resource purchasers 441 or energy grid 442 or participating in incentive programs. The cost optimization performed by asset allocator 402 can be expressed as:

$\underset{x}{\arg\min}{J(x)}$

where J(x) is defined as follows:

${J(x)} = {{\sum\limits_{sources}{\sum\limits_{horizon}{{cost}\left( {{purchase}_{{resource},{time}},{time}} \right)}}} - {\sum\limits_{incentives}{\sum\limits_{horizon}{{revenue}({ReservationAmount})}}}}$

The first term in the cost function J(x) represents the total cost of all resources purchased over the optimization horizon. Resources can include, for example, water, electricity, natural gas, or other types of resources purchased from a utility or other source 410. The second term in the cost function J(x) represents the total revenue generated by participating in incentive programs (e.g., IBDR programs) over the optimization horizon. The revenue may be based on the amount of power reserved for participating in the incentive programs. Accordingly, the total cost function represents the total cost of resources purchased minus any revenue generated from participating in incentive programs.

Each of subplants 420 and storage 430 may include equipment that can be controlled by asset allocator 402 to optimize the performance of asset allocation system 400. Subplant equipment may include, for example, heating devices, chillers, heat recovery heat exchangers, cooling towers, energy storage devices, pumps, valves, and/or other devices of subplants 420 and storage 430. Individual devices of subplants 420 can be turned on or off to adjust the resource production of each subplant 420. In some embodiments, individual devices of subplants 420 can be operated at variable capacities (e.g., operating a chiller at 10% capacity or 60% capacity) according to an operating setpoint received from asset allocator 402. Asset allocator 402 can control the equipment of subplants 420 and storage 430 to adjust the amount of each resource purchased, consumed, and/or produced by system 400.

In some embodiments, asset allocator 402 minimizes the cost function while participating in PBDR programs, IBDR programs, or simultaneously in both PBDR and IBDR programs. For the IBDR programs, asset allocator 402 may use statistical estimates of past clearing prices, mileage ratios, and event probabilities to determine the revenue generation potential of selling stored energy to resource purchasers 441 or energy grid 442. For the PBDR programs, asset allocator 402 may use predictions of ambient conditions, facility thermal loads, and thermodynamic models of installed equipment to estimate the resource consumption of subplants 420. Asset allocator 402 may use predictions of the resource consumption to monetize the costs of running the equipment.

Asset allocator 402 may automatically determine (e.g., without human intervention) a combination of PBDR and/or IBDR programs in which to participate over the optimization horizon in order to maximize economic value. For example, asset allocator 402 may consider the revenue generation potential of IBDR programs, the cost reduction potential of PBDR programs, and the equipment maintenance/replacement costs that would result from participating in various combinations of the IBDR programs and PBDR programs. Asset allocator 402 may weigh the benefits of participation against the costs of participation to determine an optimal combination of programs in which to participate. Advantageously, this allows asset allocator 402 to determine an optimal set of control decisions that maximize the overall value of operating asset allocation system 400.

In some embodiments, asset allocator 402 optimizes the cost function J(x) subject to the following constraint, which guarantees the balance between resources purchased, produced, discharged, consumed, and requested over the optimization horizon:

${{\sum\limits_{sources}{purchase}_{{resource},{time}}} + {\sum\limits_{subplants}{{produces}\left( {x_{{internal},{time}},x_{{external},{time}},v_{{uncontrolled},{time}}} \right)}} - {\sum\limits_{subplants}{{consumes}\left( {x_{{internal},{time}},x_{{external},{time}},v_{{uncontolled},{time}}} \right)}} + {\sum\limits_{storages}{{discharges}_{resource}\left( {x_{{internal},{time}},x_{{external},{time}}} \right)}} - {\sum\limits_{sinks}{requests}_{resource}}} = 0$ ∀resources, ∀time ∈ horizon

where x_(internal,time) includes internal decision variables (e.g., load allocated to each component of asset allocation system 400), x_(external,time) includes external decision variables (e.g., condenser water return temperature or other shared variables across subplants 420), and v_(uncontrolled,time) includes uncontrolled variables (e.g., weather conditions).

The first term in the previous equation represents the total amount of each resource (e.g., electricity, water, natural gas, etc.) purchased from each source 410 over the optimization horizon. The second and third terms represent the total production and consumption of each resource by subplants 420 over the optimization horizon. The fourth term represents the total amount of each resource discharged from storage 430 over the optimization horizon. Positive values indicate that the resource is discharged from storage 430, whereas negative values indicate that the resource is charged or stored. The fifth term represents the total amount of each resource requested by sinks 440 over the optimization horizon. Accordingly, this constraint ensures that the total amount of each resource purchased, produced, or discharged from storage 430 is equal to the amount of each resource consumed, stored, or provided to sinks 440.

In some embodiments, additional constraints exist on the regions in which subplants 420 can operate. Examples of such additional constraints include the acceptable space (i.e., the feasible region) for the decision variables given the uncontrolled conditions, the maximum amount of a resource that can be purchased from a given source 410, and any number of plant-specific constraints that result from the mechanical design of the plant. These additional constraints can be generated and imposed by operational domain module 904 (described in greater detail with reference to FIG. 9).

Asset allocator 402 may include a variety of features that enable the application of asset allocator 402 to nearly any central plant, central energy facility, combined heating and cooling facility, or combined heat and power facility. These features include broadly applicable definitions for subplants 420, sinks 440, storage 430, and sources 410; multiples of the same type of subplant 420 or sink 440; subplant resource connections that describe which subplants 420 can send resources to which sinks 440 and at what efficiency; subplant minimum turndown into the asset allocation optimization; treating electrical energy as any other resource that must be balanced; constraints that can be commissioned during runtime; different levels of accuracy at different points in the horizon; setpoints (or other decisions) that are shared between multiple subplants included in the decision vector; disjoint subplant operation regions; incentive based electrical energy programs; and high level airside models. Incorporation of these features may allow asset allocator 402 to support a majority of the central energy facilities that will be seen in the future. Additionally, it will be possible to rapidly adapt to the inclusion of new subplant types. Some of these features are described in greater detail below.

Broadly applicable definitions for subplants 420, sinks 440, storage 430, and sources 410 allow each of these components to be described by the mapping from decision variables to resources consume and resources produced. Resources and other components of system 400 do not need to be “typed,” but rather can be defined generally. The mapping from decision variables to resource consumption and production can change based on extrinsic conditions. Asset allocator 402 can solve the optimization problem by simply balancing resource use and can be configured to solve in terms of consumed resource 1, consumed resource 2, produced resource 1, etc., rather than electricity consumed, water consumed, and chilled water produced. Such an interface at the high level allows for the mappings to be injected into asset allocation system 400 rather than needing them hard coded. Of course, “typed” resources and other components of system 400 can still exist in order to generate the mapping at run time, based on equipment out of service.

Incorporating multiple subplants 420 or sinks 440 of the same type allows for modeling the interconnections between subplants 420, sources 410, storage 430, and sinks 440. This type of modeling describes which subplants 420 can use resource from which sources 410 and which subplants 420 can send resources to which sinks 440. This can be visualized as a resource connection matrix (i.e., a directed graph) between the subplants 420, sources 410, sinks 440, and storage 430. Examples of such directed graphs are described in greater detail with reference to FIGS. 5A-5B. Extending this concept, it is possible to include costs for delivering the resource along a connection and also, efficiencies of the transmission (e.g., amount of energy that makes it to the other side of the connection).

In some instances, constraints arise due to mechanical problems after an energy facility has been built. Accordingly, these constraints are site specific and are often not incorporated into the main code for any of subplants 420 or the high level problem itself. Commissioned constraints allow for such constraints to be added without software updates during the commissioning phase of the project. Furthermore, if these additional constraints are known prior to the plant build, they can be added to the design tool run. This would allow the user to determine the cost of making certain design decisions.

Incorporating minimum turndown and allowing disjoint operating regions may greatly enhance the accuracy of the asset allocation problem solution as well as decrease the number of modifications to solution of the asset allocation by the low level optimization or another post-processing technique. It may be beneficial to allow for certain features to change as a function of time into the horizon. One could use the full disjoint range (most accurate) for the first four hours, then switch to only incorporating the minimum turndown for the next two days, and finally using to the linear relaxation with no binary constraints for the rest of the horizon. For example, asset allocator 402 can be given the operational domain that correctly allocates three chillers with a range of 1800 to 2500 tons. The true subplant range is then the union of [1800, 2500], [3600, 5000], and [5400, 7500]. If the range were approximated as [1800, 7500] the low level optimization or other post-processing technique would have to rebalance any solution between 2500 and 3600 or between 5000 and 5400 tons. Rebalancing is typically done heuristically and is unlikely to be optimal. Incorporating these disjoint operational domains adds binary variables to the optimization problem.

Some decisions made by asset allocator 402 may be shared by multiple elements of system 400. The condenser water setpoint of cooling towers is an example. It is possible to assume that this variable is fixed and allow the low level optimization to decide on its value. However, this does not allow one to make a trade-off between the chiller's electrical use and the tower's electrical use, nor does it allow the optimization to exceed the chiller's design load by feeding it cooler condenser water. Incorporating these extrinsic decisions into asset allocator 402 allows for a more accurate solution at the cost of computational time.

Incentive programs often require the reservation of one or more assets for a period of time. In traditional systems, these assets are typically turned over to alternative control, different than the typical resource price based optimization. Advantageously, asset allocator 402 can be configured to add revenue to the cost function per amount of resource reserved. Asset allocator 402 can then make the reserved portion of the resource unavailable for typical price based cost optimization. For example, asset allocator 402 can reserve a portion of a battery asset for frequency response. In this case, the battery can be used to move the load or shave the peak demand, but can also be reserved to participate in the frequency response program.

Plant Resource Diagrams

Referring now to FIG. 5A, a plant resource diagram 500 is shown, according to an exemplary embodiment. Plant resource diagram 500 represents a particular implementation of a central plant and indicates how the equipment of the central plant are connected to each other and to external systems or devices. Asset allocator 402 can use plant resource diagram 500 to identify the interconnections between various sources 410, subplants 420, storage 430, and sinks 440 in the central plant. In some instances, the interconnections defined by diagram 500 are not capable of being inferred based on the type of resource produced. For this reason, plant resource diagram 500 may provide asset allocator 402 with new information that can be used to establish constraints on the asset allocation problem.

Plant resource diagram 500 is shown to include an electric utility 502, a water utility 504, and a natural gas utility 506. Utilities 502-506 are examples of sources 410 that provide resources to the central plant. For example, electric utility 502 may provide an electricity resource 508, water utility 504 may provide a water resource 510, and natural gas utility 506 may provide a natural gas resource 512. The lines connecting utilities 502-506 to resources 508-512 along with the directions of the lines (i.e., pointing toward resources 508-512) indicate that resources purchased from utilities 502-506 add to resources 508-512.

Plant resource diagram 500 is shown to include a chiller subplant 520, a heat recovery (HR) chiller subplant 522, a hot water generator subplant 524, and a cooling tower subplant 526. Subplants 520-526 are examples of subplants 420 that convert resource types (i.e., convert input resources to output resources). For example, the lines connecting electricity resource 508 and water resource 510 to chiller subplant 520 indicate that chiller subplant 520 receives electricity resource 508 and water resource 510 as input resources. The lines connecting chiller subplant 520 to chilled water resource 514 and condenser water resource 516 indicate that chiller subplant 520 produces chilled water resource 514 and condenser water resource 516. Similarly, the lines connecting electricity resource 508 and water resource 510 to HR chiller subplant 522 indicate that HR chiller subplant 522 receives electricity resource 508 and water resource 510 as input resources. The lines connecting HR chiller subplant 522 to chilled water resource 514 and hot water resource 518 indicate that HR chiller subplant 522 produces chilled water resource 514 and hot water resource 518.

Plant resource diagram 500 is shown to include water TES 528 and 530. Water TES 528-530 are examples of storage 530 that can be used to store and discharge resources. The line connecting chilled water resource 514 to water TES 528 indicates that water TES 528 stores and discharges chilled water resource 514. Similarly, the line connecting hot water resource 518 to water TES 530 indicates that water TES 530 stores and discharges hot water resource 518. In diagram 500, water TES 528 is connected to only chilled water resource 514 and not to any of the other water resources 516 or 518. This indicates that water TES 528 can be used by asset allocator 402 to store and discharge only chilled water resource 514 and not the other water resources 516 or 518. Similarly, water TES 530 is connected to only hot water resource 518 and not to any of the other water resources 514 or 516. This indicates that water TES 530 can be used by asset allocator 402 to store and discharge only hot water resource 518 and not the other water resources 514 or 516.

Plant resource diagram 500 is shown to include a chilled water load 532 and a hot water load 534. Loads 532-534 are examples of sinks 440 that consume resources. The line connecting chilled water load 532 to chilled water resource 514 indicates that chilled water resource 514 can be used to satisfy chilled water load 532. Similarly, the line connecting hot water load 534 to hot water resource 518 indicates that hot water resource 518 can be used to satisfy hot water load 534. Asset allocator 402 can use the interconnections and limitations defined by plant resource diagram 500 to establish appropriate constraints on the optimization problem.

Referring now to FIG. 5B, another plant resource diagram 550 is shown, according to an exemplary embodiment. Plant resource diagram 550 represents another implementation of a central plant and indicates how the equipment of the central plant are connected to each other and to external systems or devices. Asset allocator 402 can use plant resource diagram 550 to identify the interconnections between various sources 410, subplants 420, storage 430, and sinks 440 in the central plant. In some instances, the interconnections defined by diagram 550 are not capable of being inferred based on the type of resource produced. For this reason, plant resource diagram 550 may provide asset allocator 402 with new information that can be used to establish constraints on the asset allocation problem.

Plant resource diagram 550 is shown to include an electric utility 552, a water utility 554, and a natural gas utility 556. Utilities 552-556 are examples of sources 410 that provide resources to the central plant. For example, electric utility 552 may provide an electricity resource 558, water utility 554 may provide a water resource 560, and natural gas utility 556 may provide a natural gas resource 562. The lines connecting utilities 552-556 to resources 558-562 along with the directions of the lines (i.e., pointing toward resources 558-562) indicate that resources purchased from utilities 552-556 add to resources 558-562. The line connecting electricity resource 558 to electrical storage 551 indicates that electrical storage 551 can store and discharge electricity resource 558.

Plant resource diagram 550 is shown to include a boiler subplant 572, a cogeneration subplant 574, several steam chiller subplants 576-580, several chiller subplants 582-586, and several cooling tower subplants 588-592. Subplants 572-592 are examples of subplants 420 that convert resource types (i.e., convert input resources to output resources). For example, the lines connecting boiler subplant 572 and cogeneration subplant 574 to natural gas resource 562, electricity resource 558, and steam resource 564 indicate that both boiler subplant 572 and cogeneration subplant 574 consume natural gas resource 562 and electricity resource 558 to produce steam resource 564.

The lines connecting steam resource 564 and electricity resource 558 to steam chiller subplants 576-580 indicate that each of steam chiller subplants 576-580 receives steam resource 564 and electricity resource 558 as input resources. However, each of steam chiller subplants 576-580 produces a different output resource. For example, steam chiller subplant 576 produces chilled water resource 566, steam chiller subplant 578 produces chilled water resource 568, and steam chiller subplant 580 produces chilled water resource 570. Similarly, the lines connecting electricity resource 558 to chiller subplants 582-586 indicate that each of chiller subplants 582-586 receives electricity resource 558 as an input. However, each of chiller subplants 582-586 produces a different output resource. For example, chiller subplant 582 produces chilled water resource 566, chiller subplant 584 produces chilled water resource 568, and chiller subplant 586 produces chilled water resource 570.

Chilled water resources 566-570 have the same general type (i.e., chilled water) but can be defined as separate resources by asset allocator 402. The lines connecting chilled water resources 566-570 to subplants 576-586 indicate which of subplants 576-586 can produce each chilled water resource 566-570. For example, plant resource diagram 550 indicates that chilled water resource 566 can only be produced by steam chiller subplant 576 and chiller subplant 582. Similarly, chilled water resource 568 can only be produced by steam chiller subplant 578 and chiller subplant 584, and chilled water resource 570 can only be produced by steam chiller subplant 580 and chiller subplant 586.

Plant resource diagram 550 is shown to include a hot water load 599 and several cold water loads 594-598. Loads 594-599 are examples of sinks 440 that consume resources. The line connecting hot water load 599 to steam resource 564 indicates that steam resource 564 can be used to satisfy hot water load 599. Similarly, the lines connecting chilled water resources 566-570 to cold water loads 594-598 indicate which of chilled water resources 566-570 can be used to satisfy each of cold water loads 594-598. For example, only chilled water resource 566 can be used to satisfy cold water load 594, only chilled water resource 568 can be used to satisfy cold water load 596, and only chilled water resource 570 can be used to satisfy cold water load 598. Asset allocator 402 can use the interconnections and limitations defined by plant resource diagram 550 to establish appropriate constraints on the optimization problem.

Central Plant Controller

Referring now to FIG. 6, a block diagram of a central plant controller 600 in which asset allocator 402 can be implemented is shown, according to an exemplary embodiment. In various embodiments, central plant controller 600 can be configured to monitor and control central plant 200, asset allocation system 400, and various components thereof (e.g., sources 410, subplants 420, storage 430, sinks 440, etc.). Central plant controller 600 is shown providing control decisions to a building management system (BMS) 606. The control decisions provided to BMS 606 may include resource purchase amounts for sources 410, setpoints for subplants 420, and/or charge/discharge rates for storage 430.

In some embodiments, BMS 606 is the same or similar to the BMS described with reference to FIG. 1. BMS 606 may be configured to monitor conditions within a controlled building or building zone. For example, BMS 606 may receive input from various sensors (e.g., temperature sensors, humidity sensors, airflow sensors, voltage sensors, etc.) distributed throughout the building and may report building conditions to central plant controller 600. Building conditions may include, for example, a temperature of the building or a zone of the building, a power consumption (e.g., electric load) of the building, a state of one or more actuators configured to affect a controlled state within the building, or other types of information relating to the controlled building. BMS 606 may operate subplants 420 and storage 430 to affect the monitored conditions within the building and to serve the thermal energy loads of the building.

BMS 606 may receive control signals from central plant controller 600 specifying on/off states, charge/discharge rates, and/or setpoints for the subplant equipment. BMS 606 may control the equipment (e.g., via actuators, power relays, etc.) in accordance with the control signals provided by central plant controller 600. For example, BMS 606 may operate the equipment using closed loop control to achieve the setpoints specified by central plant controller 600. In various embodiments, BMS 606 may be combined with central plant controller 600 or may be part of a separate building management system. According to an exemplary embodiment, BMS 606 is a METASYS® brand building management system, as sold by Johnson Controls, Inc.

Central plant controller 600 may monitor the status of the controlled building using information received from BMS 606. Central plant controller 600 may be configured to predict the thermal energy loads (e.g., heating loads, cooling loads, etc.) of the building for plurality of time steps in an optimization period (e.g., using weather forecasts from a weather service 604). Central plant controller 600 may also predict the revenue generation potential of incentive based demand response (IBDR) programs using an incentive event history (e.g., past clearing prices, mileage ratios, event probabilities, etc.) from incentive programs 602. Central plant controller 600 may generate control decisions that optimize the economic value of operating central plant 200 over the duration of the optimization period subject to constraints on the optimization process (e.g., energy balance constraints, load satisfaction constraints, etc.). The optimization process performed by central plant controller 600 is described in greater detail below.

In some embodiments, central plant controller 600 is integrated within a single computer (e.g., one server, one housing, etc.). In various other exemplary embodiments, central plant controller 600 can be distributed across multiple servers or computers (e.g., that can exist in distributed locations). In another exemplary embodiment, central plant controller 600 may integrated with a smart building manager that manages multiple building systems and/or combined with BMS 606.

Central plant controller 600 is shown to include a communications interface 636 and a processing circuit 607. Communications interface 636 may include wired or wireless interfaces (e.g., jacks, antennas, transmitters, receivers, transceivers, wire terminals, etc.) for conducting data communications with various systems, devices, or networks. For example, communications interface 636 may include an Ethernet card and port for sending and receiving data via an Ethernet-based communications network and/or a WiFi transceiver for communicating via a wireless communications network. Communications interface 636 may be configured to communicate via local area networks or wide area networks (e.g., the Internet, a building WAN, etc.) and may use a variety of communications protocols (e.g., BACnet, IP, LON, etc.).

Communications interface 636 may be a network interface configured to facilitate electronic data communications between central plant controller 600 and various external systems or devices (e.g., BMS 606, subplants 420, storage 430, sources 410, etc.). For example, central plant controller 600 may receive information from BMS 606 indicating one or more measured states of the controlled building (e.g., temperature, humidity, electric loads, etc.) and one or more states of subplants 420 and/or storage 430 (e.g., equipment status, power consumption, equipment availability, etc.). Communications interface 636 may receive inputs from BMS 606, subplants 420, and/or storage 430 and may provide operating parameters (e.g., on/off decisions, setpoints, etc.) to subplants 420 and storage 430 via BMS 606. The operating parameters may cause subplants 420 and storage 430 to activate, deactivate, or adjust a setpoint for various devices thereof.

Still referring to FIG. 6, processing circuit 607 is shown to include a processor 608 and memory 610. Processor 608 may be a general purpose or specific purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a group of processing components, or other suitable processing components. Processor 608 may be configured to execute computer code or instructions stored in memory 610 or received from other computer readable media (e.g., CDROM, network storage, a remote server, etc.).

Memory 610 may include one or more devices (e.g., memory units, memory devices, storage devices, etc.) for storing data and/or computer code for completing and/or facilitating the various processes described in the present disclosure. Memory 610 may include random access memory (RAM), read-only memory (ROM), hard drive storage, temporary storage, non-volatile memory, flash memory, optical memory, or any other suitable memory for storing software objects and/or computer instructions. Memory 610 may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. Memory 610 may be communicably connected to processor 608 via processing circuit 607 and may include computer code for executing (e.g., by processor 608) one or more processes described herein.

Memory 610 is shown to include a building status monitor 624. Central plant controller 600 may receive data regarding the overall building or building space to be heated or cooled by system 400 via building status monitor 624. In an exemplary embodiment, building status monitor 624 may include a graphical user interface component configured to provide graphical user interfaces to a user for selecting building requirements (e.g., overall temperature parameters, selecting schedules for the building, selecting different temperature levels for different building zones, etc.).

Central plant controller 600 may determine on/off configurations and operating setpoints to satisfy the building requirements received from building status monitor 624. In some embodiments, building status monitor 624 receives, collects, stores, and/or transmits cooling load requirements, building temperature setpoints, occupancy data, weather data, energy data, schedule data, and other building parameters. In some embodiments, building status monitor 624 stores data regarding energy costs, such as pricing information available from sources 410 (energy charge, demand charge, etc.).

Still referring to FIG. 6, memory 610 is shown to include a load/rate predictor 622. Load/rate predictor 622 may be configured to predict the thermal energy loads (

_(k)) of the building or campus for each time step k (e.g., k=1 . . . n) of an optimization period. Load/rate predictor 622 is shown receiving weather forecasts from a weather service 604. In some embodiments, load/rate predictor 622 predicts the thermal energy loads

_(k) as a function of the weather forecasts. In some embodiments, load/rate predictor 622 uses feedback from BMS 606 to predict loads

_(k). Feedback from BMS 606 may include various types of sensory inputs (e.g., temperature, flow, humidity, enthalpy, etc.) or other data relating to the controlled building (e.g., inputs from a HVAC system, a lighting control system, a security system, a water system, etc.).

In some embodiments, load/rate predictor 622 receives a measured electric load and/or previous measured load data from BMS 606 (e.g., via building status monitor 624). Load/rate predictor 622 may predict loads

_(k) as a function of a given weather forecast ({circumflex over (ϕ)}_(w)), a day type (day), the time of day (t), and previous measured load data (Y_(k-1)). Such a relationship is expressed in the following equation:

_(k)=ƒ({circumflex over (ϕ)}_(w),day,t|Y _(k-1))

In some embodiments, load/rate predictor 622 uses a deterministic plus stochastic model trained from historical load data to predict loads

_(k). Load/rate predictor 622 may use any of a variety of prediction methods to predict loads

_(k) (e.g., linear regression for the deterministic portion and an AR model for the stochastic portion). Load/rate predictor 622 may predict one or more different types of loads for the building or campus. For example, load/rate predictor 622 may predict a hot water load

_(Hot,k) and a cold water load

_(Cold,k) for each time step k within the prediction window. In some embodiments, load/rate predictor 622 makes load/rate predictions using the techniques described in U.S. patent application Ser. No. 14/717,593.

Load/rate predictor 622 is shown receiving utility rates from sources 410. Utility rates may indicate a cost or price per unit of a resource (e.g., electricity, natural gas, water, etc.) provided by sources 410 at each time step k in the prediction window. In some embodiments, the utility rates are time-variable rates. For example, the price of electricity may be higher at certain times of day or days of the week (e.g., during high demand periods) and lower at other times of day or days of the week (e.g., during low demand periods). The utility rates may define various time periods and a cost per unit of a resource during each time period. Utility rates may be actual rates received from sources 410 or predicted utility rates estimated by load/rate predictor 622.

In some embodiments, the utility rates include demand charges for one or more resources provided by sources 410. A demand charge may define a separate cost imposed by sources 410 based on the maximum usage of a particular resource (e.g., maximum energy consumption) during a demand charge period. The utility rates may define various demand charge periods and one or more demand charges associated with each demand charge period. In some instances, demand charge periods may overlap partially or completely with each other and/or with the prediction window. Advantageously, demand response optimizer 630 may be configured to account for demand charges in the high level optimization process performed by asset allocator 402. Sources 410 may be defined by time-variable (e.g., hourly) prices, a maximum service level (e.g., a maximum rate of consumption allowed by the physical infrastructure or by contract) and, in the case of electricity, a demand charge or a charge for the peak rate of consumption within a certain period. Load/rate predictor 622 may store the predicted loads

_(k) and the utility rates in memory 610 and/or provide the predicted loads

_(k) and the utility rates to demand response optimizer 630.

Still referring to FIG. 6, memory 610 is shown to include an incentive estimator 620. Incentive estimator 620 may be configured to estimate the revenue generation potential of participating in various incentive-based demand response (IBDR) programs. In some embodiments, incentive estimator 620 receives an incentive event history from incentive programs 602. The incentive event history may include a history of past IBDR events from incentive programs 602. An IBDR event may include an invitation from incentive programs 602 to participate in an IBDR program in exchange for a monetary incentive. The incentive event history may indicate the times at which the past IBDR events occurred and attributes describing the IBDR events (e.g., clearing prices, mileage ratios, participation requirements, etc.). Incentive estimator 620 may use the incentive event history to estimate IBDR event probabilities during the optimization period.

Incentive estimator 620 is shown providing incentive predictions to demand response optimizer 630. The incentive predictions may include the estimated IBDR probabilities, estimated participation requirements, an estimated amount of revenue from participating in the estimated IBDR events, and/or any other attributes of the predicted IBDR events. Demand response optimizer 630 may use the incentive predictions along with the predicted loads

_(k) and utility rates from load/rate predictor 622 to determine an optimal set of control decisions for each time step within the optimization period.

Still referring to FIG. 6, memory 610 is shown to include a demand response optimizer 630. Demand response optimizer 630 may perform a cascaded optimization process to optimize the performance of asset allocation system 400. For example, demand response optimizer 630 is shown to include asset allocator 402 and a low level optimizer 634. Asset allocator 402 may control an outer (e.g., subplant level) loop of the cascaded optimization. Asset allocator 402 may determine an optimal set of control decisions for each time step in the prediction window in order to optimize (e.g., maximize) the value of operating asset allocation system 400. Control decisions made by asset allocator 402 may include, for example, load setpoints for each of subplants 420, charge/discharge rates for each of storage 430, resource purchase amounts for each type of resource purchased from sources 410, and/or an amount of each resource sold to energy purchasers 504. In other words, the control decisions may define resource allocation at each time step. The control decisions made by asset allocator 402 are based on the statistical estimates of incentive event probabilities and revenue generation potential for various IBDR events as well as the load and rate predictions.

Low level optimizer 634 may control an inner (e.g., equipment level) loop of the cascaded optimization. Low level optimizer 634 may determine how to best run each subplant at the load setpoint determined by asset allocator 402. For example, low level optimizer 634 may determine on/off states and/or operating setpoints for various devices of the subplant equipment in order to optimize (e.g., minimize) the energy consumption of each subplant while meeting the resource allocation setpoint for the subplant. In some embodiments, low level optimizer 634 receives actual incentive events from incentive programs 602. Low level optimizer 634 may determine whether to participate in the incentive events based on the resource allocation set by asset allocator 402. For example, if insufficient resources have been allocated to a particular IBDR program by asset allocator 402 or if the allocated resources have already been used, low level optimizer 634 may determine that asset allocation system 400 will not participate in the IBDR program and may ignore the IBDR event. However, if the required resources have been allocated to the IBDR program and are available in storage 430, low level optimizer 634 may determine that system 400 will participate in the IBDR program in response to the IBDR event. The cascaded optimization process performed by demand response optimizer 630 is described in greater detail in U.S. patent application Ser. No. 15/247,885.

In some embodiments, low level optimizer 634 generates and provides subplant curves to asset allocator 402. Each subplant curve may indicate an amount of resource consumption by a particular subplant (e.g., electricity use measured in kW, water use measured in L/s, etc.) as a function of the subplant load. In some embodiments, low level optimizer 634 generates the subplant curves by running the low level optimization process for various combinations of subplant loads and weather conditions to generate multiple data points. Low level optimizer 634 may fit a curve to the data points to generate the subplant curves. In other embodiments, low level optimizer 634 provides the data points asset allocator 402 and asset allocator 402 generates the subplant curves using the data points. Asset allocator 402 may store the subplant curves in memory for use in the high level (i.e., asset allocation) optimization process.

In some embodiments, the subplant curves are generated by combining efficiency curves for individual devices of a subplant. A device efficiency curve may indicate the amount of resource consumption by the device as a function of load. The device efficiency curves may be provided by a device manufacturer or generated using experimental data. In some embodiments, the device efficiency curves are based on an initial efficiency curve provided by a device manufacturer and updated using experimental data. The device efficiency curves may be stored in equipment models 618. For some devices, the device efficiency curves may indicate that resource consumption is a U-shaped function of load. Accordingly, when multiple device efficiency curves are combined into a subplant curve for the entire subplant, the resultant subplant curve may be a wavy curve. The waves are caused by a single device loading up before it is more efficient to turn on another device to satisfy the subplant load. An example of such a subplant curve is shown in FIG. 13.

Still referring to FIG. 6, memory 610 is shown to include a subplant control module 628. Subplant control module 628 may store historical data regarding past operating statuses, past operating setpoints, and instructions for calculating and/or implementing control parameters for subplants 420 and storage 430. Subplant control module 628 may also receive, store, and/or transmit data regarding the conditions of individual devices of the subplant equipment, such as operating efficiency, equipment degradation, a date since last service, a lifespan parameter, a condition grade, or other device-specific data. Subplant control module 628 may receive data from subplants 420, storage 430, and/or BMS 606 via communications interface 636. Subplant control module 628 may also receive and store on/off statuses and operating setpoints from low level optimizer 634.

Data and processing results from demand response optimizer 630, subplant control module 628, or other modules of central plant controller 600 may be accessed by (or pushed to) monitoring and reporting applications 626. Monitoring and reporting applications 626 may be configured to generate real time “system health” dashboards that can be viewed and navigated by a user (e.g., a system engineer). For example, monitoring and reporting applications 626 may include a web-based monitoring application with several graphical user interface (GUI) elements (e.g., widgets, dashboard controls, windows, etc.) for displaying key performance indicators (KPI) or other information to users of a GUI. In addition, the GUI elements may summarize relative energy use and intensity across energy storage systems in different buildings (real or modeled), different campuses, or the like. Other GUI elements or reports may be generated and shown based on available data that allow users to assess performance across one or more energy storage systems from one screen. The user interface or report (or underlying data engine) may be configured to aggregate and categorize operating conditions by building, building type, equipment type, and the like. The GUI elements may include charts or histograms that allow the user to visually analyze the operating parameters and power consumption for the devices of the energy storage system.

Still referring to FIG. 6, central plant controller 600 may include one or more GUI servers, web services 612, or GUI engines 614 to support monitoring and reporting applications 626. In various embodiments, applications 626, web services 612, and GUI engine 614 may be provided as separate components outside of central plant controller 600 (e.g., as part of a smart building manager). Central plant controller 600 may be configured to maintain detailed historical databases (e.g., relational databases, XML, databases, etc.) of relevant data and includes computer code modules that continuously, frequently, or infrequently query, aggregate, transform, search, or otherwise process the data maintained in the detailed databases. Central plant controller 600 may be configured to provide the results of any such processing to other databases, tables, XML files, or other data structures for further querying, calculation, or access by, for example, external monitoring and reporting applications.

Central plant controller 600 is shown to include configuration tools 616. Configuration tools 616 can allow a user to define (e.g., via graphical user interfaces, via prompt-driven “wizards,” etc.) how central plant controller 600 should react to changing conditions in the energy storage subsystems. In an exemplary embodiment, configuration tools 616 allow a user to build and store condition-response scenarios that can cross multiple energy storage system devices, multiple building systems, and multiple enterprise control applications (e.g., work order management system applications, entity resource planning applications, etc.). For example, configuration tools 616 can provide the user with the ability to combine data (e.g., from subsystems, from event histories) using a variety of conditional logic. In varying exemplary embodiments, the conditional logic can range from simple logical operators between conditions (e.g., AND, OR, XOR, etc.) to pseudo-code constructs or complex programming language functions (allowing for more complex interactions, conditional statements, loops, etc.). Configuration tools 616 can present user interfaces for building such conditional logic. The user interfaces may allow users to define policies and responses graphically. In some embodiments, the user interfaces may allow a user to select a pre-stored or pre-constructed policy and adapt it or enable it for use with their system.

Planning Tool

Referring now to FIG. 7, a block diagram of a planning tool 700 in which asset allocator 402 can be implemented is shown, according to an exemplary embodiment. Planning tool 700 may be configured to use demand response optimizer 630 to simulate the operation of a central plant over a predetermined time period (e.g., a day, a month, a week, a year, etc.) for planning, budgeting, and/or design considerations. When implemented in planning tool 700, demand response optimizer 630 may operate in a similar manner as described with reference to FIG. 6. For example, demand response optimizer 630 may use building loads and utility rates to determine an optimal resource allocation to minimize cost over a simulation period. However, planning tool 700 may not be responsible for real-time control of a building management system or central plant.

Planning tool 700 can be configured to determine the benefits of investing in a battery asset and the financial metrics associated with the investment. Such financial metrics can include, for example, the internal rate of return (IRR), net present value (NPV), and/or simple payback period (SPP). Planning tool 700 can also assist a user in determining the size of the battery which yields optimal financial metrics such as maximum NPV or a minimum SPP. In some embodiments, planning tool 700 allows a user to specify a battery size and automatically determines the benefits of the battery asset from participating in selected IBDR programs while performing PBDR. In some embodiments, planning tool 700 is configured to determine the battery size that minimizes SPP given the IBDR programs selected and the requirement of performing PBDR. In some embodiments, planning tool 700 is configured to determine the battery size that maximizes NPV given the IBDR programs selected and the requirement of performing PBDR.

In planning tool 700, asset allocator 402 may receive planned loads and utility rates for the entire simulation period. The planned loads and utility rates may be defined by input received from a user via a client device 722 (e.g., user-defined, user selected, etc.) and/or retrieved from a plan information database 726. Asset allocator 402 uses the planned loads and utility rates in conjunction with subplant curves from low level optimizer 634 to determine an optimal resource allocation (i.e., an optimal dispatch schedule) for a portion of the simulation period.

The portion of the simulation period over which asset allocator 402 optimizes the resource allocation may be defined by a prediction window ending at a time horizon. With each iteration of the optimization, the prediction window is shifted forward and the portion of the dispatch schedule no longer in the prediction window is accepted (e.g., stored or output as results of the simulation). Load and rate predictions may be predefined for the entire simulation and may not be subject to adjustments in each iteration. However, shifting the prediction window forward in time may introduce additional plan information (e.g., planned loads and/or utility rates) for the newly-added time slice at the end of the prediction window. The new plan information may not have a significant effect on the optimal dispatch schedule since only a small portion of the prediction window changes with each iteration.

In some embodiments, asset allocator 402 requests all of the subplant curves used in the simulation from low level optimizer 634 at the beginning of the simulation. Since the planned loads and environmental conditions are known for the entire simulation period, asset allocator 402 may retrieve all of the relevant subplant curves at the beginning of the simulation. In some embodiments, low level optimizer 634 generates functions that map subplant production to equipment level production and resource use when the subplant curves are provided to asset allocator 402. These subplant to equipment functions may be used to calculate the individual equipment production and resource use (e.g., in a post-processing module) based on the results of the simulation.

Still referring to FIG. 7, planning tool 700 is shown to include a communications interface 704 and a processing circuit 706. Communications interface 704 may include wired or wireless interfaces (e.g., jacks, antennas, transmitters, receivers, transceivers, wire terminals, etc.) for conducting data communications with various systems, devices, or networks. For example, communications interface 704 may include an Ethernet card and port for sending and receiving data via an Ethernet-based communications network and/or a WiFi transceiver for communicating via a wireless communications network. Communications interface 704 may be configured to communicate via local area networks or wide area networks (e.g., the Internet, a building WAN, etc.) and may use a variety of communications protocols (e.g., BACnet, IP, LON, etc.).

Communications interface 704 may be a network interface configured to facilitate electronic data communications between planning tool 700 and various external systems or devices (e.g., client device 722, results database 728, plan information database 726, etc.). For example, planning tool 700 may receive planned loads and utility rates from client device 722 and/or plan information database 726 via communications interface 704. Planning tool 700 may use communications interface 704 to output results of the simulation to client device 722 and/or to store the results in results database 728.

Still referring to FIG. 7, processing circuit 706 is shown to include a processor 710 and memory 712. Processor 710 may be a general purpose or specific purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a group of processing components, or other suitable processing components. Processor 710 may be configured to execute computer code or instructions stored in memory 712 or received from other computer readable media (e.g., CDROM, network storage, a remote server, etc.).

Memory 712 may include one or more devices (e.g., memory units, memory devices, storage devices, etc.) for storing data and/or computer code for completing and/or facilitating the various processes described in the present disclosure. Memory 712 may include random access memory (RAM), read-only memory (ROM), hard drive storage, temporary storage, non-volatile memory, flash memory, optical memory, or any other suitable memory for storing software objects and/or computer instructions. Memory 712 may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. Memory 712 may be communicably connected to processor 710 via processing circuit 706 and may include computer code for executing (e.g., by processor 710) one or more processes described herein.

Still referring to FIG. 7, memory 712 is shown to include a GUI engine 716, web services 714, and configuration tools 718. In an exemplary embodiment, GUI engine 716 includes a graphical user interface component configured to provide graphical user interfaces to a user for selecting or defining plan information for the simulation (e.g., planned loads, utility rates, environmental conditions, etc.). Web services 714 may allow a user to interact with planning tool 700 via a web portal and/or from a remote system or device (e.g., an enterprise control application).

Configuration tools 718 can allow a user to define (e.g., via graphical user interfaces, via prompt-driven “wizards,” etc.) various parameters of the simulation such as the number and type of subplants, the devices within each subplant, the subplant curves, device-specific efficiency curves, the duration of the simulation, the duration of the prediction window, the duration of each time step, and/or various other types of plan information related to the simulation. Configuration tools 718 can present user interfaces for building the simulation. The user interfaces may allow users to define simulation parameters graphically. In some embodiments, the user interfaces allow a user to select a pre-stored or pre-constructed simulated plant and/or plan information (e.g., from plan information database 726) and adapt it or enable it for use in the simulation.

Still referring to FIG. 7, memory 712 is shown to include demand response optimizer 630. Demand response optimizer 630 may use the planned loads and utility rates to determine an optimal resource allocation over a prediction window. The operation of demand response optimizer 630 may be the same or similar as previously described with reference to FIG. 6. With each iteration of the optimization process, demand response optimizer 630 may shift the prediction window forward and apply the optimal resource allocation for the portion of the simulation period no longer in the prediction window. Demand response optimizer 630 may use the new plan information at the end of the prediction window to perform the next iteration of the optimization process. Demand response optimizer 630 may output the applied resource allocation to reporting applications 730 for presentation to a client device 722 (e.g., via user interface 724) or storage in results database 728.

Still referring to FIG. 7, memory 712 is shown to include reporting applications 730. Reporting applications 730 may receive the optimized resource allocations from demand response optimizer 630 and, in some embodiments, costs associated with the optimized resource allocations. Reporting applications 730 may include a web-based reporting application with several graphical user interface (GUI) elements (e.g., widgets, dashboard controls, windows, etc.) for displaying key performance indicators (KPI) or other information to users of a GUI. In addition, the GUI elements may summarize relative energy use and intensity across various plants, subplants, or the like. Other GUI elements or reports may be generated and shown based on available data that allow users to assess the results of the simulation. The user interface or report (or underlying data engine) may be configured to aggregate and categorize resource allocation and the costs associated therewith and provide the results to a user via a GUI. The GUI elements may include charts or histograms that allow the user to visually analyze the results of the simulation. An exemplary output that may be generated by reporting applications 730 is shown in FIG. 8.

Referring now to FIG. 8, several graphs 800 illustrating the operation of planning tool 700 are shown, according to an exemplary embodiment. With each iteration of the optimization process, planning tool 700 selects an optimization period (i.e., a portion of the simulation period) over which the optimization is performed. For example, planning tool 700 may select optimization period 802 for use in the first iteration. Once the optimal resource allocation 810 has been determined, planning tool 700 may select a portion 818 of resource allocation 810 to send to plant dispatch 830. Portion 818 may be the first b time steps of resource allocation 810. Planning tool 700 may shift the optimization period 802 forward in time, resulting in optimization period 804. The amount by which the prediction window is shifted may correspond to the duration of time steps b.

Planning tool 700 may repeat the optimization process for optimization period 804 to determine the optimal resource allocation 812. Planning tool 700 may select a portion 820 of resource allocation 812 to send to plant dispatch 830. Portion 820 may be the first b time steps of resource allocation 812. Planning tool 700 may then shift the prediction window forward in time, resulting in optimization period 806. This process may be repeated for each subsequent optimization period (e.g., optimization periods 806, 808, etc.) to generate updated resource allocations (e.g., resource allocations 814, 816, etc.) and to select portions of each resource allocation (e.g., portions 822, 824) to send to plant dispatch 830. Plant dispatch 830 includes the first b time steps 818-824 from each of optimization periods 802-808. Once the optimal resource allocation is compiled for the entire simulation period, the results may be sent to reporting applications 730, results database 728, and/or client device 722, as described with reference to FIG. 7.

Asset Allocator

Referring now to FIG. 9, a block diagram illustrating asset allocator 402 in greater detail is shown, according to an exemplary embodiment. Asset allocator 402 may be configured to control the distribution, production, storage, and usage of resources in a central plant. As discussed above, asset allocator 402 can be configured to minimize the economic cost (or maximize the economic value) of operating a central plant over the duration of the optimization period. The economic cost may be defined by a cost function J(x) that expresses economic cost as a function of the control decisions made by asset allocator 402. The cost function J(x) may account for the cost of resources purchased from sources 410, as well as the revenue generated by selling resources to resource purchasers 441 or energy grid 442 or participating in incentive programs.

In some embodiments, asset allocator 402 performs an optimization process determine an optimal set of control decisions for each time step within an optimization period. The control decisions may include, for example, an optimal amount of each resource to purchase from sources 410, an optimal amount of each resource to produce or convert using subplants 420, an optimal amount of each resource to store or remove from storage 430, an optimal amount of each resource to sell to resources purchasers 441 or energy grid 440, and/or an optimal amount of each resource to provide to other sinks 440. In some embodiments, asset allocator 402 is configured to optimally dispatch all campus energy assets in order to meet the requested heating, cooling, and electrical loads of the campus for each time step within the optimization period.

Throughout this disclosure, asset allocator 402 is described as actively identifying or defining various items (e.g., sources 410, subplants 420, storage 430, sinks 440, operational domains, etc.). However, it should be understood that asset allocator 402 can also, or alternatively, receive such items as inputs. For example, the existence of such items can be defined by a user (e.g., via a user interface) or any other data source (e.g., another algorithm, an external system or process, etc.). Asset allocator 402 can be configured to identify which of these items have been defined or identified and can generate an appropriate cost function and optimization constraints based on the existence of these items. It should be understood that the acts of identifying or defining these items can include asset allocator 402 identifying, detecting, receiving, or otherwise obtaining a predefined item an input.

Optimization Framework

Asset allocator 402 is shown to include an optimization framework module 902. Optimization framework module 902 can be configured to define an optimization framework for the optimization problem solved by asset allocator 402. In some embodiments, optimization framework module 902 defines the optimization problem as a mixed integer linear program (MILP). The MILP framework provides several advantages over the linear programming framework used in previous systems. For example, the MILP framework can account for minimum turndowns on equipment, can ensure that the high level optimization problem computes a point on the subplant curve for heat recovery chillers, and can impose logical constraints on the optimization problem to compensate for poor mechanical design and/or design inefficiencies.

In some embodiments, the MILP created by optimization framework module 902 has the following form:

${\min\limits_{x,z}c_{x}^{T}x} + {c_{z}^{T}z}$

subject to the following constraints:

A _(x) x+A _(z) z≤b

H _(x) x+H _(z) z=g

z=integer

where x∈

^(n) ^(x) is a vector of the continuous decision variables, z∈

^(n) ^(z) is a vector of the integer decision variables, c_(x) and c_(z) are the respective cost vectors for the continuous decision variables and integer decision variables, A_(x), A_(z), and b are the matrices and vector that describe the inequality constraints, and H_(x), H_(z), and g are the matrices and vector that describe the equality constraints.

Optimization Problem Construction

Still referring to FIG. 9, asset allocator 402 is shown to include an optimization problem constructor 910. Optimization problem constructor 910 can be configured to construct the high level (i.e., asset allocation) optimization problem solved by asset allocator 402. In some embodiments, the high level optimization problem includes one or more of the elements of asset allocation system 400. For example, the optimization problem can include sinks 440, sources 410, subplants 420, and storage 430, as described with reference to FIG. 4. In some embodiments, the high level optimization problem includes airside units, which can be considered a type of energy storage in the mass of the building. The optimization problem may include site-specific constraints that can be added to compensate for mechanical design deficiencies.

In some embodiments, the optimization problem generated by optimization problem constructor 910 includes a set of links between sources 410, subplants 420, storage 430, sinks 440, or other elements of the optimization problem. For example, the high level optimization problem can be viewed as a directed graph, as shown in FIGS. 5A-5B. The nodes of the directed graph can include sources 410, subplants 420, storage 430, and sinks 440. The set of links can define the connections between the nodes, the cost of the connections between nodes (e.g., distribution costs), the efficiency of each connection, and the connections between site-specific constraints.

In some embodiments, the optimization problem generated by optimization problem constructor 910 includes an objective function. The objective function can include the sum of predicted utility usage costs over the horizon (i.e., the optimization period), the predicted demand charges, the total predicted incentive revenue over the prediction horizon, the sum of the predicted distribution costs, the sum of penalties on unmet and overmet loads over the prediction horizon, and/or the sum of the rate of change penalties over the prediction horizon (i.e., delta load penalties). All of these terms may add to the total cost, with the exception of the total predicted incentive revenue. The predicted incentive revenue may subtract from the total cost. For example, the objective function generated by optimization problem constructor 910 may have the following form:

${J(x)} = {{\sum\limits_{k = 1}^{h}\left( {{Source}{Usage}{Cost}} \right)_{k}} + \left( {{Total}{Demand}{Charges}} \right) - \left( {{Total}{Incentives}} \right) + {\sum\limits_{k = 1}^{h}\left( {{Distribution}{Cost}} \right)_{k}} + {\sum\limits_{k = 1}^{h}\left( {{{Unmet}/{Overmet}}{Load}{Penalties}} \right)_{k}} + {\sum\limits_{k = 1}^{h}\left( {{Rate}{of}{Change}{Penalties}} \right)_{k}}}$

where the index k denotes a time step in the optimization period and h is the total number of time steps in the optimization period.

In some embodiments, the optimization problem generated by optimization problem constructor 910 includes a set of constraints. The set of constraints can include resource balance constraints (e.g., hot water balance, chilled water balance, electricity balance, etc.), operational domain constraints for each of subplants 420, state of charge (SOC) and storage capacity constraints for each of storage 430, decision variable constraints (e.g., subplant capacity constraints, charge and discharge of storage constraints, and storage capacity constraints), demand/peak usage constraints, auxiliary constraints, and any site specific or commissioned constraints. In some embodiments, the operational domain constraints are generalized versions of the subplant curves. The operational domain constraints can be generated by operational domain module 904 (described in greater detail below). The decision variable constraints may be box constraints of the form x_(lb)≤x≤x_(ub), where x is a decision variable and x_(lb) and x_(ub) are the lower and upper bound for the decision variable x.

The optimization problem generated by optimization problem constructor 910 can be considered a finite-horizon optimal control problem. The optimization problem may take the form:

minimize J(x)

subject to resource balances, operational domains for subplants 420 (e.g., subplant curves), constraints to predict the SOC of storage 430, storage capacity constraints, subplant/storage box constraints (e.g., capacity constraints and discharge/charge rate constraints), demand/peak usage constraints, auxiliary constraints for rate of change variables, auxiliary constraints for demand charges, and site specific constraints.

In some embodiments, optimization problem constructor 910 applies an inventory balance constraint to each resource. One side of the inventory balance constraint for a given resource may include the total amount of the resource purchased from all sources 410, the total amount of the resource produced by all of subplants 420, the total amount of the resource discharged from storage 430 (negative values indicate charging storage 430), and unmet load. The other side of the inventory balance for the resource may include the total amount of the resource requested/predicted (uncontrolled load), carryover from the previous time step, the total amount of the resource consumed by all subplants 420 and airside units, overmet load, and the total amount of the resource sold. For example, the inventory balance for a resource may have the form:

${{\sum\limits_{i \in {\{{Sources}\}}}\left( {{Purchased}{Resource}} \right)_{i}} + {\sum\limits_{j \in {\{{Subplants}\}}}\left( {{Produced}{Resource}} \right)_{j}} + {\sum\limits_{k \in {\{{Storage}\}}}\left( {{Discharged}{Storage}} \right)_{k}} + {{Unmet}{Load}}} = {{{Requested}{Load}} + {Carryover} + {\sum\limits_{j \in {\{{Subplants}\}}}{\left( {{Consumed}{Resource}} \right)_{j}{\sum\limits_{l \in {\{{{Airside}{Units}}\}}}\left( {{Consumed}{Resource}} \right)_{l}}}} + {{Overmet}{Load}} + {{Resource}{Sold}}}$

Optimization problem constructor 910 may require this resource balance to be satisfied for each resource at each time step of the optimization period. Together the unmet and overmet load capture the accumulation of a resource. Negative accumulation (unmet load) are distinguished from positive accumulation (overmet load) because typically, overmet loads are not included in the resource balance. Even though unmet and overmet loads are listed separately, at most one of the two may be non-zero. The amount of carryover may be the amount of unmet/overmet load from the previous time step (described in greater detail below). The requested load may be determined by load/rate predictor 622 and provided as an input to the high level optimization problem.

Throughout this disclosure, the high level/asset allocator optimization problem or high level/asset allocator problem refers to the general optimization problem constructed by optimization problem constructor 910. A high level problem instance refers to a realization of the high level problem provided the input data and parameters. The high level optimization/asset allocation algorithm refers to the entire set of steps needed to solve a high level problem instance (i.e., encapsulates both the set of mathematical operations and the implementation or software design required to setup and solve a high level problem instance. Finally, a high level problem element or high level element refers to any of the elements of the high level problem including sinks 440, sources 410, subplants 420, storage 430, or airside unit.

Element Models

Still referring to FIG. 9, asset allocator 402 is shown to include element models 930. Element models 930 may store definitions and/or models for various elements of the high level optimization problem. For example, element models 930 are shown to include sink models 932, source models 934, subplant models 936, storage models 938, and element links 940. In some embodiments, element models 930 include data objects that define various attributes or properties of sinks 440, sources 410, subplants 420, and storage 430 (e.g., using object-oriented programming).

For example, source models 934 may define the type of resource provided by each of sources 410, a cost of each resource, demand charges associated with the consumption of the resource, a maximum rate at which the resource can be purchased from each of sources 410, and other attributes of sources 410. Similarly, subplant models 936 may define the input resources of each subplant 420, the output resources of each subplant 420, relationships between the input and output variables of each subplant 420 (i.e., the operational domain of each subplant 420), and optimization constraints associated with each of subplants 420. Each of element models 930 are described in greater detail below.

Sink Models

Element models 930 are shown to include sink models 932. Sink models 932 may store models for each of sinks 440. As described above, sinks 440 may include resource consumers or requested loads. Some examples are the campus thermal loads and campus electricity usage. The predicted consumption of a sink 440 over the optimization period can be supplied as an input to asset allocator 401 and/or computed by load/rate predictor 622. Sink models 932 may store the predicted consumption over the optimization period for each of sinks 440. Sink models 932 may also store any unmet/overmet load for each of sinks 440, carryover from the previous time steps, and any incentives earned by supplying each of sinks 440 (e.g., for sinks such as an energy purchasers or an energy grid).

Carryover can be defined as the amount of unmet or overmet load for a particular resource from the previous time step. In some embodiments, asset allocator 402 determines the carryover by adding the entire unmet load for a particular resource in one time step to the requested load for the resource at the next time step. However, calculating the carryover in this manner may not always be appropriate since the carryover may grow over time. As an example, consider an unmet chilled water load. If there are several time steps where the chilled water load is not met, the buildings supplied by the load will heat up. Due to this increase in building temperature, the amount of chilled water load required to decrease the building temperature to the set-point is not a linearly increasing function of the sum of the unmet load over the past time steps because the building temperature will begin approaching the ambient temperature.

In some embodiments, asset allocator 402 adds a forgetting factor to the carryover. For example, asset allocator 402 can calculate the carryover for each time step using the following equation:

carryover_(j+1)=γ_(j)·unmet/overmet_(j)

where unmet/overmet_(j) is the amount of unmet and/or overmet load at time step j, carryover_(j+1) is the carryover added to the right-hand side of the inventory balance at the next time step j+1, and γ_(j)∈[0,1] is the forgetting factor. Selecting γ_(j)=0 corresponds to case where no unmet/overmet load is carried over to the next time step, whereas selecting γ_(j)=1 corresponds to case where all unmet/overmet load is carried over to the next time step. An intermediate selection of γ_(j) (i.e., 0≤γ_(j)≤1) corresponds to the case where some, but not all, of the unmet/overmet load is carried over. For the case of a chilled water system, the choice of γ_(j) may depend on the plant itself and can be determined using the amount of unmet load that actually stored in the water (temperature would increase above the setpoint) when an unmet load occurs.

Source Models

Still referring to FIG. 9, element models 930 are shown to include source models 934. Source models 934 may store models for each of sources 410. As described above, sources 410 may include utilities or markets where resources may be purchased. Source models 934 may store a price per unit of a resource purchased from each of sources 410 (e.g., $/kWh of electricity, $/liter of water, etc.). This cost can be included as a direct cost associated with resource usage in the cost function. In some embodiments, source models 934 store costs associated with demand charges and demand constraints, incentive programs (e.g., frequency response and economic demand response) and/or sell back programs for one or more of sources 410.

In some embodiments, the cost function J(x) includes a demand charge based on peak electrical usage during a demand charge period (e.g., during a month). This demand charge may be based on the maximum rate of electricity usage at any time in the demand charge period. There are several other types of demand charges besides the anytime monthly demand charge for electricity including, for example, time-of-day monthly and yearlong ratchets. Some or all of these demand charges can be added to the cost function depending on the particular types of demand charges imposed by sources 410. In some embodiments, demand charges are defined as follows:

$wc\max\limits_{i \in T_{demand}}\left\{ x_{i} \right\}$

where x_(i) represents the resource purchase at time step i of the optimization period, c>0 is the demand charge rate, w is a (potentially time-varying) weight applied to the demand charge term to address any discrepancies between the optimization period and the time window over which the demand charge is applied, and T_(demand)⊆{1, . . . , h} is the subinterval of the optimization period to which the demand charge is applied. Source models 934 can store values for some or all of the parameters that define the demand charges and the demand charge periods.

In some embodiments, asset allocator 402 accounts for demand charges within a linear programming framework by introducing an auxiliary continuous variable. This technique is described in greater detail with reference to demand charge module 906. While this type of term may readily be cast into a linear programming framework, it can be difficult to determine the weighting coefficient w when the demand charge period is different from the optimization period. Nevertheless, through a judicious choice of the two adjustable parameters for demand charges (i.e., the weighting coefficient w and the initial value of the auxiliary demand variable), other types of demand charges may be included in the high level optimization problem.

In some embodiments, source models 934 store parameters of various incentive programs offered by sources 410. For example, the source definition 934 for an electric utility may define a capability clearing price, a performance clearing price, a regulation award, or other parameters that define the benefits (e.g., potential revenue) of participating in a frequency regulation program. In some embodiments, source models 934 define a decision variable in the optimization problem that accounts for the capacity of a battery reserved for frequency regulation. This variable effectively reduces the capacity of the battery that is available for priced-based demand response. Depending on the complexity of the decision, source models 934 may also define a decision variable that indicates whether to participate in the incentive program. In asset allocator 402, storage capacity may be reserved for participation in incentive programs. Low level optimizer 634 can then be used to control the reserved capacity that is charged/discharged for the incentive program (e.g., frequency response control).

In some embodiments, source models 934 store pricing information for the resources sold by sources 410. The pricing information can include time-varying pricing information, progressive or regressive resource prices (e.g., prices that depend on the amount of the resource purchased), or other types of pricing structures. Progressive and regressive resource prices may readily be incorporated into the optimization problem by leveraging the set of computational operations introduced by the operational domain. In the case of either a progressive rate that is a discontinuous function of the usage or for any regressive rate, additional binary variables can be introduced into the optimization problem to properly describe both of these rates. For progressive rates that are continuous functions of the usage, no binary variables are needed because one may apply a similar technique as that used for imposing demand charges.

Referring now to FIG. 10, a graph 1000 depicting a progressive rate structure for a resource is shown, according to an exemplary embodiment. The cost per unit of the resource purchased can be described by the following continuous function:

${Cost} = \left\{ \begin{matrix} {{{p_{1}u} + b_{1}},} & {{{if}u} \in \left\lbrack {0,u_{1}} \right\rbrack} \\ {{{p_{2}u} + b_{2}},} & {{{if}u} \in \left\lbrack {u_{1},u_{2}} \right\rbrack} \\ {{{p_{3}u} + b_{3}},} & {{{if}u} \in \left\lbrack {u_{2},u_{3}} \right\rbrack} \end{matrix} \right.$

where p_(i) is the price of the ith interval, b_(i) is the offset of the ith interval, u is the amount of the resource purchased, and p_(i)u_(i)+b_(i)=p_(i+1)u_(i)+b_(i) for i=1, 2. Although the rate depicted in graph 1000 represents a cost, negative prices may be used to account for profits earned by selling back resources. Source models 934 can store values for some of all of these parameters in order to fully define the cost of resource purchases and/or the revenue generated from resource sales.

In the cost function J(x), the following term can be used to describe progressive rates:

$\max\limits_{i \in {\{{1,2,3}\}}}\left\{ {{p_{i}u} + b_{i}} \right\}$

Since the goal is to minimize cost, this term can be equivalently described in the optimization problem by introducing an auxiliary continuous variable C and the following constraints:

C≥0

p ₁ u+b ₁ ≤C

p ₂ u+b ₂ ≤C

p ₂ u+b ₂ ≤C

where C is the auxiliary variable that is equal to the cost of the resource. Source models 934 can define these constraints in order to enable progressive rate structures in the optimization problem.

In some embodiments, source models 934 stores definitions of any fixed costs associated with resource purchases from each of sources 410. These costs can be captured within the MILP framework. For example, let v∈{0,1} represent whether a source 410 is being utilized (v=0 means the source 410 is not used and v=1 means the source 410 is used) and let u∈[0, u_(max)] be the source usage where u_(max) represents the maximum usage. If the maximum usage is not known, u_(max) may be any arbitrarily large number that satisfies u<u_(max). Then, the following two constraints ensure that the binary variable v is zero when u=1 and is one when u>0:

u−u _(max) v≤0

u≥0

Asset allocator 402 can add the term c_(fixed)v to the cost function to account for fixed costs associated with each of sources 410, where C_(fixed) is the fixed cost. Source models 934 can define these constraints and terms in order to account for fixed costs associated with sources 410.

Subplant Models

Referring again to FIG. 9, element models 930 are shown to include subplant models 936. Subplant models 936 may store models for each of subplants 420. As discussed above, subplants 420 are the main assets of a central plant. Subplants 420 can be configured to convert resource types, making it possible to balance requested loads from the building or campus using resources purchased from sources 410. This general definition allows for a diverse set of central plant configurations and equipment types as well as varying degrees of subplant modeling fidelity and resolution.

In some embodiments, subplant models 936 identify each of subplants 420 as well as the optimization variables associated with each subplant. The optimization variables of a subplant can include the resources consumed, the resources produced, intrinsic variables, and extrinsic variables. Intrinsic variables may be internal to the optimization formulation and can include any auxiliary variables used to formulate the optimization problem. Extrinsic variables may be variables that are shared among subplants (e.g., condenser water temperature).

In some embodiments, subplant models 936 describe the relationships between the optimization variables of each subplant. For example, subplant models 936 can include subplant curves that define the output resource production of a subplant as a function of one or more input resources provided to the subplant. In some embodiments, operational domains are used to describe the relationship between the subplant variables. Mathematically, an operational domain is a union of a collection of polytopes in an n-dimensional (real) space that describe the admissible set of variables of a high level element. Operational domains are described in greater detail below.

In some embodiments, subplant models 936 store subplant constraints for each of subplants 420. Subplant constraints may be written in the following general form:

A _(x,j) x _(j) +A _(z,j) z _(j) ≤b _(j)

H _(x,j) x _(j) +H _(z,j) z _(j) =g _(j)

X _(lb,j) ≤X _(j) x _(ub,j)

z _(lb,j) ≤z _(j) ≤z _(ub,j)

z _(j)=integer

for all j where j is an index representing the jth subplant, x_(j) denotes the continuous variables associated with the jth subplant (e.g., resource variables and auxiliary optimization variables), and z_(j) denotes the integer variables associated with the jth subplant (e.g., auxiliary binary optimization variables). The vectors x_(lb,j), x_(ub,j), z_(lb,j,) and z_(ub,j) represent the box (bound) constraints on the decision variables. The matrices A_(x,j), A_(z,j), H_(x,j), and H_(z,j) and the vectors b_(j) and g_(j) are associated with the inequality constraints and the equality constraints for the jth subplant.

In some embodiments, subplant models 936 store the input data used to generate the subplant constraints. Such input data may include sampled data points of the high level subplant curve/operational domain. For example, for chiller subplant 422, this data may include several points sampled from the subplant curve 1300 (shown in FIG. 13). When implemented as part of an online operational tool (shown in FIG. 6), the high level subplant operational domain can be sampled by querying low level optimizer 634 at several requested production amounts. When implemented as part of an offline planning tool (shown in FIG. 7), the sampled data may be user-specified efficiency and capacity data.

Storage Models

Referring again to FIG. 9, element models 930 are shown to include storage models 938. Storage models 938 may store models for each of storage 430. Storage models 938 can define the types of resources stored by each of storage 430, as well as storage constraints that limit the state-of-charge (e.g., maximum charge level) and/or the rates at which each storage 430 can be charged or discharged. In some embodiments, the current level or capacity of storage 430 is quantified by the state-of-charge (SOC), which can be denoted by ϕ where ϕ=0 corresponds to empty and ϕ=1 corresponds to full. To describe the SOC as a function of the charge rate or discharge rate, a dynamic model can be stored as part of storage models 938. The dynamic model may have the form:

ϕ(k+1)=Aϕ(k)+Bu(k)

where ϕ(k) is the predicted state of charge at time step k of the optimization period, u(k) is the charge/discharge rate at time step k, and A and B are coefficients that account for dissipation of energy from storage 430. In some embodiments, A and B are time-varying coefficients. Accordingly, the dynamic model may have the form:

ϕ(k+1)=A(k)ϕ(k)+B(k)u(k)

where A(k) and B(k) are coefficients that vary as a function of the time step k.

Asset allocator 402 can be configured to add constraints based on the operational domain of storage 430. In some embodiments, the constraints link decision variables adjacent in time as defined by the dynamic model. For example, the constraints may link the decision variables ϕ(k+1) at time step k+1 to the decision variables ϕ(k) and u(k) at time step k. In some embodiments, the constraints link the SOC of storage 430 to the charge/discharge rate. Some or all of these constraints may be defined by the dynamic model and may depend on the operational domain of storage 430.

In some embodiments, storage models 938 store optimization constraints for each of storage 430. Storage constraints may be written in the following general form:

A _(x,k) x _(k) +A _(z,k) z _(k) ≤b _(k)

H _(x,k) x _(k) +H _(z,k) z _(k) =g _(k)

x _(lb,k) ≤X _(k) ≤x _(ub,k)

z _(lb,k) ≤z _(k) ≤z _(ub,k)

z _(k)=integer

for all k where k is an index representing the kth storage device, x_(k) denotes the continuous variables associated with the kth storage device (e.g., resource variables and auxiliary optimization variables), and z_(k) denotes the integer variables associated with the kth storage device (e.g., auxiliary binary optimization variables). The vectors x_(lb,k), x_(ub,k), z_(lb,k), and z_(ub,k) represent the box (bound) constraints on the decision variables. The matrices A_(x,k), A_(z,k), and H_(z,k) and the vectors b_(k) and g_(k) are associated with the inequality constraints and the equality constraints for the kth storage device.

The optimization constraints may ensure that the predicted SOC for each of storage 430 is maintained between a minimum SOC Q_(min) and a maximum SOC Q_(max). The optimization constraints may also ensure that the charge/discharge rate is maintained between a minimum charge rate {dot over (Q)}_(min) and maximum charge rate {dot over (Q)}_(max). In some embodiments, the optimization constraints include terminal constraints imposed on the SOC at the end of the optimization period. For example, the optimization constraints can ensure that one or more of storage 430 are full at the end of the optimization period (i.e., “tank forced full” constraints).

In some embodiments, storage models 938 store mixed constraints for each of storage 430. Mixed constraints may be needed in the case that the operational domain of storage 430 is similar to that shown in FIG. 11. FIG. 11 is a graph 1100 of an example operational domain for a thermal energy storage tank or thermal energy storage subplant (e.g., TES subplants 431-432). Graph 1100 illustrates a scenario in which the discharge rate is limited to less than a maximum discharge rate at low SOCs, whereas the charge rate is limited to less than a maximum charge rate at high SOCs. In a thermal energy storage tank, the constraints on the discharge rate at low SOCs may be due to mixing between layers of the tank. For TES subplants 431-432 and the TES tanks that form TES subplants 431-432, the SOC represents the fraction of the current tank level or:

$\phi = \frac{Q - Q_{\min}}{Q_{\max} - Q_{\min}}$

where Q is the current tank level, Q_(min) is the minimum tank level, Q_(max) is the maximum tank level, and ϕ∈[0,1] is the SOC. Since the maximum rate of discharge or charge may depend on the SOC at low or high SOC, SOC dependent bounds on the maximum rate of discharge or charge may be included.

In some embodiments, storage models 938 store SOC models for each of storage 430. The SOC model for a thermal energy storage tank may be an integrator model given by:

${\phi\left( {k + 1} \right)} = {{\phi(k)} - {\delta t_{s}\frac{\overset{.}{Q}(k)}{Q_{\max} - Q_{\min}}}}$

where {dot over (Q)}(k) is the charge/discharge rate and δt_(s). Positive values of {dot over (Q)}(k) represent discharging, whereas negative values of {dot over (Q)}(k) represent charging. The mixed constraints depicted in FIG. 11 can be accounted for as follows:

a _(mixed)ϕ(k)+b _(mixed) ≤{dot over (Q)}(k)

0≤ϕ(k)≤1

−{dot over (Q)} _(charge,max) ≤{dot over (Q)}(k)≤{dot over (Q)} _(discharge,max)

where a_(mixed) and b_(mixed) are vectors of the same dimension that describe any mixed linear inequality constraints (e.g., constraints that depend on both the SOC and the discharge/charge rate). The second constraint (i.e., 0≤ϕ(k)≤1) is the constraint on the SOC. The last constraint limits the rate of charging and discharging within bound.

In some embodiments, storage models 938 include models that treat the air within the building and/or the building mass as a form of energy storage. However, one of the key differentiators between an airside mass and storage 430 is that additional care must be taken to ensure feasibility of the optimization problem (e.g., soft constraining of the state constraints). Nevertheless, airside optimization units share many common features and mathematical operations as storage 430. In some embodiments, a state-space representation of airside dynamics can be used to describe the predicted evolution of airside optimization units (e.g., building mass). Such a model may have the form:

x(k+1)=Ax(k)+Bu(k)

where x(k) is the airside optimization unit state vector, u(k) is the airside optimization unit input vector, and A and B are the system matrices. In general, an airside optimization unit or the control volume that the dynamic model describes may represent a region (e.g., multiple HVAC zones served by the same air handling unit) or an aggregate of several regions (e.g., an entire building).

Element Links

Still referring to FIG. 9, element models 930 are shown to include element links 940. In some embodiments, element links 940 define the connections between sources 410, subplants 420, storage 430, and sinks 440. These links 940 are shown as lines connecting various elements in plant resource diagrams 500 and 550. For example, element links 940 may define which of sources 410 provide resources to each of subplants 420, which subplants 420 are connected to which storage 430, and which subplants 420 and/or storage 430 provide resources to each of sinks 440. Element links 940 may contain the data and methods needed to create and solve an instance of the high level optimization problem.

In some embodiments, element links 940 link sources 410, subplants 420, storage 430, and sinks 440 (i.e., the high level problem elements) using a netlist of connections between high level problem elements. The information provided by element links 940 may allow multiple subplants 420, storage 430, sinks 440, and sources of the same type to be defined. Rather than assuming that all elements contribute to and draw from a common pool of each resource, element links 940 can be used to specify the particular connections between elements. Accordingly, multiple resources of the same type can be defined such that a first subset of subplants 420 produce a first resource of a given type (e.g., Chilled Water A), whereas a second subset of subplants 420 produce a second resource of the same type (e.g., Chilled Water B). Such a configuration is shown in FIG. 5B. Advantageously, element links 940 can be used to build constraints that reflect the actual physical connections between equipment in a central plant.

In some embodiments, element links 940 are used to account for the distribution costs of resources between elements of asset allocation system 400 (e.g., from sources 410 to subplants 420, from subplants 420 to sinks 440, etc.) and/or the distribution efficiency of each connection. In some cases it may be necessary to include costs for delivering the resource along a connection, or an efficiency of the transportation (amount or percentage of resources received on the other side of the connection). Accounting for distribution costs and/or distribution efficiency may affect the result of the optimization in some situations. For example, consider a first chiller subplant 420 that is highly efficient and can provide a chilled water resource to sinks 440, but it costs significantly more (e.g., due to pumping costs etc.) to transport the resource from the first chiller subplant 420 rather than from a second chiller subplant 420. In that scenario, asset allocator 402 may determine that the first chiller subplant 420 should be used only if necessary. Additionally, energy could be lost during transportation along a particular connection (e.g., chilled water temperature may increase over a long pipe). This could be described as an efficiency of the connection.

The resource balance constraint can be modified to account for distribution efficiency as follows:

${{\sum\limits_{sources}{\alpha_{{source},{resource}}{purchase}_{{resource},{time}}}} + {\sum\limits_{subplants}{\alpha_{{subplant},{resource}}{{produces}\left( {x_{{internal},{time}},x_{{external},{time}},v_{{uncontrolled},{time}}} \right)}}} - {\sum\limits_{subplants}{\frac{1}{\alpha_{{source},{resource}}}{consumes}\left( {x_{{internal},{time}},x_{{external},{time}},v_{{uncontrolled},{time}}} \right)}} + {\sum\limits_{storages}{{discharges}_{resource}\left( {x_{{internal},{time}},x_{{external},{time}}} \right)}} - {\frac{1}{\alpha_{{sink},{resource}}}{\sum\limits_{sinks}{requests}_{resource}}}} = 0$ ∀resources, ∀time ∈ horizon

where the α terms are loss factors with values between zero and one.

The cost function can be modified to account for transportation costs as follows:

${J(x)} = {{\sum\limits_{sources}{\sum\limits_{horizon}{{cost}\left( {{purchase}_{{resource},{time}},{time}} \right)}}} + \ldots + {\sum\limits_{connection}{\lambda_{connection}{resource}_{connection}}}}$

where λ_(connection) is the cost per unit resource transported along a particular connection and resource_(connection) is the amount of the resource transported along the connection. Accordingly, the final term of the cost function accounts for transportation costs along each of the connections or links between elements in asset allocation system 400.

Demand Charges

Still referring to FIG. 9, asset allocator 402 is shown to include a demand charge module 906. Demand charge module 906 can be configured to modify the cost function J(x) and the optimization constraints to account for one or more demand charges. As previously described, demand charges are costs imposed by sources 410 based on the peak consumption of a resource from sources 410 during various demand charge periods (i.e., the peak amount of the resource purchased from the utility during any time step of the applicable demand charge period). For example, an electric utility may define one or more demand charge periods and may impose a separate demand charge based on the peak electric consumption during each demand charge period. Electric energy storage can help reduce peak consumption by storing electricity in a battery when energy consumption is low and discharging the stored electricity from the battery when energy consumption is high, thereby reducing peak electricity purchased from the utility during any time step of the demand charge period.

In some instances, one or more of the resources purchased from 410 are subject to a demand charge or multiple demand charges. There are many types of potential demand charges as there are different types of energy rate structures. The most common energy rate structures are constant pricing, time of use (TOU), and real time pricing (RTP). Each demand charge may be associated with a demand charge period during which the demand charge is active. Demand charge periods can overlap partially or completely with each other and/or with the optimization period. Demand charge periods can include relatively long periods (e.g., monthly, seasonal, annual, etc.) or relatively short periods (e.g., days, hours, etc.). Each of these periods can be divided into several sub-periods including off-peak, partial-peak, and/or on-peak. Some demand charge periods are continuous (e.g., beginning Jan. 1, 2017 and ending Jan. 31, 2017), whereas other demand charge periods are non-continuous (e.g., from 11:00 AM-1:00 PM each day of the month).

Over a given optimization period, some demand charges may be active during some time steps that occur within the optimization period and inactive during other time steps that occur during the optimization period. Some demand charges may be active over all the time steps that occur within the optimization period. Some demand charges may apply to some time steps that occur during the optimization period and other time steps that occur outside the optimization period (e.g., before or after the optimization period). In some embodiments, the durations of the demand charge periods are significantly different from the duration of the optimization period.

Advantageously, demand charge module 906 may be configured to account for demand charges in the high level optimization process performed by asset allocator 402. In some embodiments, demand charge module 906 incorporates demand charges into the optimization problem and the cost function J(x) using demand charge masks and demand charge rate weighting factors. Each demand charge mask may correspond to a particular demand charge and may indicate the time steps during which the corresponding demand charge is active and/or the time steps during which the demand charge is inactive. Each rate weighting factor may also correspond to a particular demand charge and may scale the corresponding demand charge rate to the time scale of the optimization period.

The demand charge term of the cost function J(x) can be expressed as:

${J(x)} = {\ldots{\sum\limits_{s \in {sources}}{\sum\limits_{q \in {demands}_{s}}{w_{{demand},s,q}r_{{demand},s,q}{\max\limits_{i \in {demand}_{s,q}}\left( {purchase}_{s,i} \right)}\ldots}}}}$

where the max( ) function selects the maximum amount of the resource purchased from source s during any time step i that occurs during the optimization period. However, the demand charge period associated with demand charge q may not cover all of the time steps that occur during the optimization period. In order to apply the demand charge q to only the time steps during which the demand charge q is active, demand charge module 906 can add a demand charge mask to the demand charge term as shown in the following equation:

${J(x)} = {\ldots{\sum\limits_{s \in {sources}}{\sum\limits_{q \in {demands}_{s}}{w_{{demand},s,q}r_{{demand},s,q}{\max\limits_{i \in {demand}_{s,q}}\left( {g_{s,q,i}{purchase}_{s,i}} \right)}\ldots}}}}$

where g_(s,q,i) is an element of the demand charge mask.

The demand charge mask may be a logical vector including an element g_(s,q,i) for each time step i that occurs during the optimization period. Each element g_(s,q,i) of the demand charge mask may include a binary value (e.g., a one or zero) that indicates whether the demand charge q for source s is active during the corresponding time step i of the optimization period. For example, the element g_(s,q,i) may have a value of one (i.e., g_(s,q,i)=1) if demand charge q is active during time step i and a value of zero (i.e., g_(s,q,ti)=0) if demand charge q is inactive during time step i. An example of a demand charge mask is shown in the following equation:

g _(s,q)=[0, 0, 0, 1, 1, 1, 1, 0, 0, 0, 1, 1]^(T)

where g_(s,q,1), g_(s,q,2), g_(s,q,3), g_(s,q,8), g_(s,q,9), and g_(s,q,10) have values of zero, whereas g_(s,q,4), g_(s,q,5), g_(s,q,6), g_(s,q,7), g_(s,q,11), and g_(s,q,12) have values of one. This indicates that the demand charge q is inactive during time steps i=1, 2, 3, 8, 9, 10 (i.e., g_(s,q,i)=0 ∀i=1, 2, 3, 8, 9, 10) and active during time steps i=4, 5, 6, 7, 11, 12 (i.e., g_(s,q,i)=1 ∀i=4, 5, 6, 7, 11, 12). Accordingly, the term g_(s,q,i)purchase_(s,i) within the max( ) function may have a value of zero for all time steps during which the demand charge q is inactive. This causes the max( ) function to select the maximum purchase from source s that occurs during only the time steps for which the demand charge q is active.

In some embodiments, demand charge module 906 calculates the weighting factor w_(demand,s,q) for each demand charge q in the cost function J(x). The weighting factor w_(demand,s,q) may be a ratio of the number of time steps the corresponding demand charge q is active during the optimization period to the number of time steps the corresponding demand charge q is active in the remaining demand charge period (if any) after the end of the optimization period. For example, demand charge module 906 can calculate the weighting factor w_(demand,s,q) using the following equation:

$w_{{demand},s,q} = \frac{\sum_{i = k}^{k + h - 1}g_{s,q,i}}{\sum_{i = {k + h}}^{period\_ end}g_{s,q,i}}$

where the numerator is the summation of the number of time steps the demand charge q is active in the optimization period (i.e., from time step k to time step k+h−1) and the denominator is the number of time steps the demand charge q is active in the portion of the demand charge period that occurs after the optimization period (i.e., from time step k+h to the end of the demand charge period).

The following example illustrates how demand charge module 906 can incorporate multiple demand charges into the cost function J(x). In this example, a single source of electricity (e.g., an electric grid) is considered with multiple demand charges applicable to the electricity source (i.e., q=1 . . . N, where N is the total number of demand charges). The system includes a battery asset which can be allocated over the optimization period by charging or discharging the battery during various time steps. Charging the battery increases the amount of electricity purchased from the electric grid, whereas discharging the battery decreases the amount of electricity purchased from the electric grid.

Demand charge module 906 can modify the cost function J(x) to account for the N demand charges as shown in the following equation:

${J(x)} = {\ldots + {w_{d_{1}}r_{d_{1}}{\max\limits_{i}\left( {g_{1_{i}}\left( {{- P_{{bat}_{i}}} + {eLoad}_{i}} \right)} \right)}} + \ldots + {w_{d_{q}}r_{d_{q}}{\max\limits_{i}\left( {g_{q_{i}}\left( {{- P_{{bat}_{i}}} + {eLoad}_{i}} \right)} \right)}} + \ldots + {w_{d_{N}}r_{d_{N}}{\max\limits_{i}\left( {g_{N_{i}}\left( {{- P_{{bat}_{i}}} + {eLoad}_{i}} \right)} \right)}}}$

where the term −P_(bat) _(i) +eLoad_(i) represents the total amount of electricity purchased from the electric grid during time step i (i.e., the total electric load eLoad_(i) minus the power discharged from the battery P_(bat) _(i) ). Each demand charge q=1 N can be accounted for separately in the cost function J(x) by including a separate max( ) function for each of the N demand charges. The parameter r_(d) _(q) indicates the demand charge rate associated with the qth demand charge (e.g., $/kW) and the weighting factor w_(d) _(q) indicates the weight applied to the qth demand charge.

Demand charge module 906 can augment each max( ) function with an element g_(q) _(i) of the demand charge mask for the corresponding demand charge. Each demand charge mask may be a logical vector of binary values which indicates whether the corresponding demand charge is active or inactive at each time step i of the optimization period. Accordingly, each max( ) function may select the maximum electricity purchase during only the time steps the corresponding demand charge is active. Each max( ) function can be multiplied by the corresponding demand charge rate r_(d) _(q) and the corresponding demand charge weighting factor w_(d) _(q) to determine the total demand charge resulting from the battery allocation P_(bat) over the duration of the optimization period.

In some embodiments, demand charge module 906 linearizes the demand charge terms of the cost function J(x) by introducing an auxiliary variable d_(q) for each demand charge q. In the case of the previous example, this will result in N auxiliary variables d₁ . . . d_(N) being introduced as decision variables in the cost function J(x). Demand charge module 906 can modify the cost function J(x) to include the linearized demand charge terms as shown in the following equation:

J(x)= . . . +w _(d) ₁ r _(d) ₁ d ₁ + . . . +w _(d) _(q) r _(d) _(q) d _(q) + . . . +w _(d) _(N) r _(d) _(N) d _(N)

Demand charge module 906 can impose the following constraints on the auxiliary demand charge variables d₁ . . . d_(N) to ensure that each auxiliary demand charge variable represents the maximum amount of electricity purchased from the electric utility during the applicable demand charge period:

d₁ ≥ g_(1_(i))(−P_(bat_(i)) + eLoad_(i))∀i = k…k + h − 1, g_(1_(i)) ≠ 0 d₁ ≥ 0⋮ d_(q) ≥ g_(q_(i))(−P_(bat_(i)) + eLoad_(i))∀i = k…k + h − 1, g_(q_(i)) ≠ 0 d_(q) ≥ 0⋮ d_(N) ≥ g_(N_(i))(−P_(bat_(i)) + eLoad_(i))∀i = k…k + h − 1, g_(N_(i)) ≠ 0 d_(N) ≥ 0

In some embodiments, the number of constraints corresponding to each demand charge q is dependent on how many time steps the demand charge q is active during the optimization period. For example, the number of constraints for the demand charge q may be equal to the number of non-zero elements of the demand charge mask g_(q). Furthermore, the value of the auxiliary demand charge variable d_(q) at each iteration of the optimization may act as the lower bound of the value of the auxiliary demand charge variable d_(q) at the following iteration.

Consider the following example of a multiple demand charge structure. In this example, an electric utility imposes three monthly demand charges. The first demand charge is an all-time monthly demand charge of 15.86 $/kWh which applies to all hours within the entire month. The second demand charge is an on-peak monthly demand charge of 1.56 $/kWh which applies each day from 12:00-18:00. The third demand charge is a partial-peak monthly demand charge of 0.53 $/kWh which applies each day from 9:00-12:00 and from 18:00-22:00.

For an optimization period of one day and a time step of one hour (i.e., i=1 . . . 24), demand charge module 906 may introduce three auxiliary demand charge variables. The first auxiliary demand charge variable d₁ corresponds to the all-time monthly demand charge; the second auxiliary demand charge variable d₂ corresponds to the on-peak monthly demand charge; and the third auxiliary demand charge variable d₃ corresponds to the partial-peak monthly demand charge. Demand charge module 906 can constrain each auxiliary demand charge variable to be greater than or equal to the maximum electricity purchase during the hours the corresponding demand charge is active, using the inequality constraints described above.

Demand charge module 906 can generate a demand charge mask g_(q) for each of the three demand charges (i.e., q=1 . . . 3), where g_(q) includes an element for each time step of the optimization period (i.e., g_(q)=[g_(q1) . . . g_(q24)). The three demand charge masks can be defined as follows:

g ₁ _(i) =1 ∀i=1 . . . 24

g ₂ _(i) =1 ∀i=12 . . . 18

g ₃ _(i) =1 ∀i=9 . . . 12, 18 . . . 22

with all other elements of the demand charge masks equal to zero. In this example, it is evident that more than one demand charge constraint will be active during the hours which overlap with multiple demand charge periods. Also, the weight of each demand charge over the optimization period can vary based on the number of hours the demand charge is active, as previously described.

In some embodiments, demand charge module 906 considers several different demand charge structures when incorporating multiple demand charges into the cost function J(x) and optimization constraints. Demand charge structures can vary from one utility to another, or the utility may offer several demand charge options. In order to incorporate the multiple demand charges within the optimization framework, a generally-applicable framework can be defined as previously described. Demand charge module 906 can translate any demand charge structure into this framework. For example, demand charge module 906 can characterize each demand charge by rates, demand charge period start, demand charge period end, and active hours. Advantageously, this allows demand charge module 906 to incorporate multiple demand charges in a generally-applicable format.

The following is another example of how demand charge module 906 can incorporate multiple demand charges into the cost function J(x). Consider, for example, monthly demand charges with all-time, on-peak, partial-peak, and off-peak. In this case, there are four demand charge structures, where each demand charge is characterized by twelve monthly rates, twelve demand charge period start (e.g., beginning of each month), twelve demand charge period end (e.g., end of each month), and hoursActive. The hoursActive is a logical vector where the hours over a year where the demand charge is active are set to one. When running the optimization over a given horizon, demand charge module 906 can implement the applicable demand charges using the hoursActive mask, the relevant period, and the corresponding rate.

In the case of an annual demand charge, demand charge module 906 can set the demand charge period start and period end to the beginning and end of a year. For the annual demand charge, demand charge module 906 can apply a single annual rate. The hoursActive demand charge mask can represent the hours during which the demand charge is active. For an annual demand charge, if there is an all-time, on-peak, partial-peak, and/or off-peak, this translates into at most four annual demand charges with the same period start and end, but different hoursActive and different rates.

In the case of a seasonal demand charge (e.g., a demand charge for which the maximum peak is determined over the indicated season period), demand charge module 906 can represent the demand charge as an annual demand charge. Demand charge module 906 can set the demand charge period start and end to the beginning and end of a year. Demand charge module 906 can set the hoursActive to one during the hours which belong to the season and to zero otherwise. For a seasonal demand charge, if there is an All-time, on-peak, partial, and/or off-peak, this translates into at most four seasonal demand charges with the same period start and end, but different hoursActive and different rates.

In the case of the average of the maximum of current month and the average of the maxima of the eleven previous months, demand charge module 906 can translate the demand charge structure into a monthly demand charge and an annual demand charge. The rate of the monthly demand charge may be half of the given monthly rate and the annual rate may be the sum of given monthly rates divided by two. These and other features of demand charge module 906 are described in greater detail in U.S. patent application Ser. No. 15/405,236 filed Jan. 12, 2017, the entire disclosure of which is incorporated by reference herein.

Incentive Programs

Referring again to FIG. 9, asset allocator 402 is shown to include an incentive program module 908. Incentive program module 908 may modify the optimization problem to account for revenue from participating in an incentive-based demand response (IBDR) program. IBDR programs may include any type of incentive-based program that provides revenue in exchange for resources (e.g., electric power) or a reduction in a demand for such resources. For example, asset allocation system 400 may provide electric power to an energy grid or an independent service operator as part of a frequency response program (e.g., PJM frequency response) or a synchronized reserve market. In a frequency response program, a participant contracts with an electrical supplier to maintain reserve power capacity that can be supplied or removed from an energy grid by tracking a supplied signal. The participant is paid by the amount of power capacity required to maintain in reserve. In other types of IBDR programs, asset allocation system 400 may reduce its demand for resources from a utility as part of a load shedding program. It is contemplated that asset allocation system 400 may participate in any number and/or type of IBDR programs.

In some embodiments, incentive program module 908 modifies the cost function J(x) to include revenue generated from participating in an economic load demand response (ELDR) program. ELDR is a type of IBDR program and similar to frequency regulation. In ELDR, the objective is to maximize the revenue generated by the program, while using the battery to participate in other programs and to perform demand management and energy cost reduction. To account for ELDR program participation, incentive program module 908 can modify the cost function J(x) to include the following term:

$\max\limits_{b_{i},P_{{bat}_{i}}}\left( {- {\sum\limits_{i = k}^{k + h - 1}{b_{i}{r_{{ELDR}_{i}}\left( {{adjCBL}_{i} - \left( {{eLoad}_{i} - P_{{bat}_{i}}} \right)} \right)}}}} \right)$

where b_(i) is a binary decision variable indicating whether to participate in the ELDR program during time step i, r_(ELDR) _(i) is the ELDR incentive rate at which participation is compensated, and adjCBL_(i) is the symmetric additive adjustment (SAA) on the baseline load. The previous expression can be rewritten as:

$\min\limits_{b_{i},P_{{bat}_{i}}}\left( {- {\sum\limits_{i = k}^{k + h - 1}{b_{i}{r_{{ELDR}_{i}}\left( {{\sum\limits_{l = 1}^{4}\frac{e_{li}}{4}} + {\sum\limits_{p = {m - 4}}^{m - 2}{\frac{1}{3}\left( {{eLoad}_{p} - P_{{bat}_{p}} - {\sum\limits_{l = 1}^{4}\frac{e_{lp}}{4}} - \left( {{eLoad}_{i} - \underset{l = 1}{P_{{bat}_{i}}}} \right)} \right)}}} \right)}}}} \right.$

where e_(li) and e_(lp) are the electric loads at the lth hour of the operating day.

In some embodiments, incentive program module 908 handles the integration of ELDR into the optimization problem as a bilinear problem with two multiplicative decision variables. In order to linearize the cost function J(x) and customize the ELDR problem to the optimization framework, several assumptions may be made. For example, incentive program module 908 can assume that ELDR participation is only in the real-time market, balancing operating reserve charges and make whole payments are ignored, day-ahead prices are used over the horizon, real-time prices are used in calculating the total revenue from ELDR after the decisions are made by the optimization algorithm, and the decision to participate in ELDR is made in advance and passed to the optimization algorithm based on which the battery asset is allocated.

In some embodiments, incentive program module 908 calculates the participation vector b_(i) as follows:

$b_{i} = \left\{ \begin{matrix} 1 & {\forall{{{i/r_{{DA}_{i}}} \geq {{NBT}_{i}{and}i}} \in S}} \\ 0 & {otherwise} \end{matrix} \right.$

where r_(DA) _(i) is the hourly day-ahead price at the ith hour, NBT_(i) is the net benefits test value corresponding to the month to which the corresponding hour belongs, and S is the set of nonevent days. Nonevent days can be determined for the year by choosing to participate every x number of days with the highest day-ahead prices out of y number of days for a given day type. This approach may ensure that there are nonevent days in the 45 days prior to a given event day when calculating the CBL for the event day.

Given these assumptions and the approach taken by incentive program module 908 to determine when to participate in ELDR, incentive program module 908 can adjust the cost function J(x) as follows:

${J(x)} = {{- {\sum\limits_{i = k}^{k + h - 1}{r_{e_{i}}P_{{bat}_{i}}}}} - {\sum\limits_{i = k}^{k + h - 1}{r_{{FR}_{i}}P_{{FR}_{i}}}} + {\sum\limits_{i = k}^{k + h - 1}{r_{s_{i}}s_{i}}} + {w_{d}r_{d}d} - {\sum\limits_{i = k}^{k + h - 1}{b_{i}{r_{{DA}_{i}}\left( {{\sum\limits_{p = {m - 4}}^{m - 2}{{- \frac{1}{3}}P_{{bat}_{p}}}} + P_{{bat}_{i}}} \right)}}}}$

where b_(i) and m are known over a given horizon. The resulting term corresponding to ELDR shows that the rates at the ith participation hour are doubled and those corresponding to the SAA are lowered. This means it is expected that high level optimizer 632 will tend to charge the battery during the SAA hours and discharge the battery during the participation hours. Notably, even though a given hour is set to be an ELDR participation hour, high level optimizer 632 may not decide to allocate any of the battery asset during that hour. This is due to the fact that it may be more beneficial at that instant to participate in another incentive program or to perform demand management.

To build the high level optimization problem, optimization problem constructor 910 may query the number of decision variables and constraints that each subplant 420, source 410, storage 430, and site specific constraint adds to the problem. In some embodiments, optimization problem constructor 910 creates optimization variable objects for each variable of the high level problem to help manage the flow of data. After the variable objects are created, optimization problem constructor 910 may pre-allocate the optimization matrices and vectors for the problem. Element links 940 can then be used to fill in the optimization matrices and vectors by querying each component. The constraints associated with each subplant 420 can be filled into the larger problem-wide optimization matrix and vector. Storage constraints can be added, along with demand constraints, demand charges, load balance constraints, and site-specific constraints.

Extrinsic Variables

In some embodiments, asset allocator 402 is configured to optimize the use of extrinsic variables. Extrinsic variables can include controlled or uncontrolled variables that affect multiple subplants 420 (e.g., condenser water temperature, external conditions such as outside air temperature, etc.). In some embodiments, extrinsic variables affect the operational domain of multiple subplants 420. There are many methods that can be used to optimize the use of extrinsic variables. For example, consider a chiller subplant connected to a cooling tower subplant. The cooling tower subplant provides cooling for condenser water provided as an input to the chiller. Several scenarios outlining the use of extrinsic variables in this example are described below.

In a first scenario, both the chiller subplant and the tower subplant have operational domains that are not dependent on the condenser water temperatures. In this scenario, the condenser water temperature can be ignored (e.g., excluded from the set of optimization variables) since the neither of the operational domains are a function of the condenser water temperature.

In a second scenario, the chiller subplant has an operational domain that varies with the entering condenser water temperature. However, the cooling tower subplant has an operational domain that is not a function of the condenser water temperature. For example, the cooling tower subplant may have an operational domain that defines a relationship between fan power and water usage, independent from its leaving condenser water temperature or ambient air wet bulb temperature. In this case, the operational domain of the chiller subplant can be sliced (e.g., a cross section of the operational domain can be taken) at the condenser water temperature indicated at each point in the optimization period.

In a third scenario, the cooling tower subplant has an operational domain that depends on its leaving condenser water temperature. Both the entering condenser water temperature of the chiller subplant and the leaving condenser water temperature of the cooling tower subplant can be specified so the operational domain will be sliced at those particular values. In both the second scenario and the third scenario, asset allocator 402 may produce variables for the condenser water temperature. In the third scenario, asset allocator 402 may produce the variables for both the tower subplant and the chiller subplant. However, these variables will not become decision variables because they are simply specified directly

In a fourth scenario, the condenser water temperature affects the operational domains of both the cooling tower subplant and the chiller subplant. Because the condenser water temperature is not specified, it may become an optimization variable that can be optimized by asset allocator 402. In this scenario, the optimization variable is produced when the first subplant (i.e., either the chiller subplant or the cooling tower subplant) reports its optimization size. When the second subplant is queried, no additional variable is produced. Instead, asset allocator 402 may recognize the shared optimization variable as the same variable from the connection netlist.

When asset allocator 402 asks for constraints from the individual subplants 420, subplants 420 may send those constraints using local indexing. Asset allocator 402 may then disperse these constraints by making new rows in the optimization matrix, but also distributing the column to the correct columns based on its own indexing for the entire optimization problem. In this way, extrinsic variables such as condenser water temperature can be incorporated into the optimization problem in an efficient and optimal manner.

Commissioned Constraints

Some constraints may arise due to mechanical problems after the energy facility has been built. These constraints are site specific and may not be incorporated into the main code for any of the subplants or the high level problem itself. Instead, constraints may be added without software update on site during the commissioning phase of the project. Furthermore, if these additional constraints are known prior to the plant build they could be added to the design tool run. Commissioned constraints can be held by asset allocator 402 and can be added constraints to any of the ports or connections of subplants 420. Constraints can be added for the consumption, production, or extrinsic variables of a subplant.

As an example implementation, two new complex type internals can be added to the problem. These internals can store an array of constraint objects that include a dictionary to describe inequality and equality constraints, times during which the constraints are active, and the elements of the horizon the constraints affect. In some embodiments, the dictionaries have keys containing strings such as (subplantUserName)·(portInternalName) and values that represent the linear portion of the constraint for that element of the constraint matrix. A special “port name” could exist to reference whether the subplant is running. A special key can be used to specify the constant part of the constraint or the right hand side. A single dictionary can describe a single linear constraint. More detail regarding asset allocator 402 and related systems and methods is described in U.S. patent application Ser. No. 15/473,493 filed Mar. 29, 2017, the entirety of which is incorporated by reference herein.

Planning Tool User Interface

Referring now to FIGS. 10-44, several examples of user interface 724 are shown, according to various embodiments. As discussed above, user interface 724 may be generated by planning tool 700 and displayed to a user via client device 722. Client device 722 may be a personal computer, laptop, smartphone, tablet, workstation, or any other type of suitable computing device. In some embodiments, planning tool 700 is implemented as a cloud-based SaaS (i.e., software as a service) application and can be accessed via an electronic network (e.g., via web services 714). Planning tool 700 may be used by personnel such as application engineers, commissioning engineers, and technicians to facilitate the design of a central plant.

In some embodiments, some or all components of demand response optimizer 630 can be implemented as an integrated simulation engine service A3S (i.e., application as a service) external to planning tool 700. In such embodiments, demand response optimizer 630 receives simulation data (e.g., equipment models 720, weather forecasts, planned loads and utility rates, etc.) from planning tool 700 and applies an algorithm in order to generate simulation results. The simulation results may then be returned and planning tool 700 can perform further calculations (e.g., derive cost, determine best fit model) to be presented via user interface 724.

Users of planning tool 700 can create a central plant model through user interface 724. Such a central plant model may include sources 410, subplants 420, storage 430, and sinks 440 (e.g., element models 930), for example. Proper configuration of the central plant model within planning tool 700 can result in more accurate simulations and therefore more efficient design of the central plant. Users of planning tool 700 may struggle to properly configure the central plant model if user interface 724 does not help guide them in an effective manner. The user interfaces described in FIGS. 10-44 are examples of an improved user interface 724 that is effective in assisting users to properly configure a central plant customized for their application. Advantageously, user interface 724 may prevent users from making invalid or improper connections between include sources 410, subplants 420, storage 430, and sinks 440 as users are designing the central plant model. For example, a user may try to connect a hot water output of a subplant to a cold water sink. In this example, planning tool 700 may recognize this input as invalid by comparing to a set of rules that define valid relationships between sources 410, subplants 420, storage 430, and sinks 440 as described in more detail below. As such, user interface 724 may prevent the user from making such a connection.

FIG. 10 illustrates a create model dialog box 1002 of interface 724 that can be used to create a new central plant model. The create model dialog box can be accessed from a model editor home page. The model editor home page can show any and all plant models associated with a project file. The project file, for example, may be associated with a building, a building campus, a customer (e.g., business entity using planning tool 700), etc. Interface 724 is shown to include a file tree 1010 that can be used to select different project files and associated models, data, scenarios, and simulations. File tree 1010 is also shown to include a search bar that can be react to different search queries entered by users. As shown in FIG. 10, the current project file contains four models and the user is creating a fifth model using the create model dialog box. The create model dialog box allows the user to name the model (e.g., “Plant Design E”), associate the model with one or more tags (e.g., “Chillers”), and enter a text description of the model. The user may then save the new model by clicking the save button of the create dialog box. Once saved successfully, the new model appears on a model list 1004 the model editor home page as shown in FIG. 11. Interface 724 may provide feedback 1006 to indicate that the model has been successfully added. Models can be edited, copied, or deleted from model list 1006 (e.g., by clicking the symbols in the “action” column). Model list 1004 may also include a status indicator for each model shown as either a green box that reads “complete” or a red box that reads “incomplete.” In addition, the model list 1004 may include a date associated with the model (e.g., creation date, last edited date), an indication of a user (e.g., user ID) that created the model, and any tags or description associated with the model.

FIG. 12 illustrates a model editor page for the newly created plant model entitled “Plant Design E.” The model editor page includes a workspace 1300 as well as a symbol palette 1200. Symbol palette 1200 can include a variety of symbols that represent different sources 410, subplants 420, storage 430, or sinks 440. Accordingly, symbol palette 1200 is shown to include a supplier tab 1210, a plant tab 1220, a loads tab 1230, and a storage tab 1240. As shown in FIG. 12, the user has selected supplier tab 1210 and can select from an electricity supplier symbol 1211 and an electricity supplier symbol 1212. The symbols may be stored in a symbol library and each may be associated with different properties or rules. The user can drag symbols from symbol palette 1200 into workspace 1300 in order to begin creating a central plant model. For example, FIG. 13 shows that a user has dragged a water supplier symbol 1311 and an electricity supplier symbol 1312 onto workspace 1300. Users can save a plant model at any time by selecting a save button and can cancel any changes made to a plant model at any time my selecting a cancel button as shown in FIG. 12.

As illustrated in FIG. 14, the user has dragged a second electricity supplier symbol 1313 onto workspace 1300. Moreover, the user may right click using a mouse pointer 1402 on any symbols in workspace 1300 at any time in order to perform actions such as copying, pasting, or deleting the symbol. In addition, the user may also access a property panel 1502 associated with the symbol as shown in FIG. 15. The property panel may allow the user to enter a customized name for the symbol and specify constraints associated with the symbol, for example. The constraints can include resource balance constraints, operational domain constraints, state of charge and storage capacity constraints, decision variable constraints, demand/peak usage constraints, auxiliary constraints, and/or site specific constraints, for example, as described above. Property panel 1502 is associated with an electricity supplier, however it will be appreciated that property panels may include different information for different symbols.

Turning now to FIG. 16, the user has selected plant tab 1220 of symbol palette 1200 in order to access subplant symbols such as a chiller plant symbol 1221, a chiller tower plant symbol 122, a tower plant symbol 1223, and an air cooled chiller plant symbol 1224. As shown in FIG. 16, the user has dragged a tower plant symbol 1321, a chiller plant symbol 1322, and a chiller tower plant symbol 1323 onto workspace 1300. Turning to FIG. 17, the user has selected loads tab 1230 in order to access a chilled water load symbol 1231. The user has also dragged a chilled water load symbol 1331 onto workspace 1300. Turning to FIG. 18, the user has selected storage tab 1240 in order to access a chilled water thermal storage tank symbol 1241.

The user can hover over any of the symbols on workspace 1300 in order to create connections between the symbols. As shown in FIG. 19, when the user moves mouse pointer 1402 over water supplier symbol 1311, two connection points (point 1911 on the left and point 1912 on the right) appear. As shown in FIG. 20, the user may click and drag from connection point 1912 of water supplier symbol 1311 to a connection point of tower plant symbol 1321 in order to form a connection between water supplier symbol 1311 and tower plant symbol 1321. Once the connection is formed, a connection 2101 may be created between water supplier symbol 1311 and tower plant symbol 1321 on interface 724 as shown in FIG. 21. Planning tool 700 can be configured to display connection 2101 as an animated light blue line on interface 724 to indicate that a water resource is being transferred between the energy devices. Also shown in FIG. 21 is a connection 2102 that the user has formed between the water supplier symbol 1311 and chiller tower plant symbol 1323. As shown in FIGS. 21 and 22, the user can use mouse pointer 1402 to select connection 2102 and adjust the positioning of the connection lines between symbols 1311. The user may also use mouse pointer 1402 to adjust the position of any symbols in the workspace at any time.

As shown in FIG. 23, the user has created a connection 2103 between the electricity supplier symbol 1312 and the tower plant symbol 1321. Planning tool 700 can be configured to display connection 2103 on interface 724 as an animated orange or yellow line to indicate that an electricity resource is being transferred between the energy devices. Moreover, also shown in FIG. 23, the user may attempt to form a connection between water supplier symbol 1311 and chilled water load 1331. This is an example of an improper or invalid connection that planning tool 700 will prevent the user from making. For example, planning tool 700 may evaluate this user input according to the set of rules that define valid relationships between sources 410, subplants 420, storage 430, and sinks 440 as described in more detail below.

FIG. 24 illustrates further connections made by the user between the symbols in workspace 1300. For example, the user has formed a connection 2104 between electricity supplier 1312 and chiller plant 1322. In addition, the user has formed a connection 2105 between electricity supplier 1313 and chiller tower plant 1323, a connection 2106 between chiller plant 1322 and tower plant 1321, a connection 2107 between chiller plant 1322 and chilled water load 1331, and a connection 2108 between chiller tower plant 1323 and chilled water load 1331. Connection 2106 may be displayed as an animated green line to indicate that a condenser water resource is being transferred whereas connections 2107 and 2108 may be animated dark blue lines to indicate that a chilled water resource is being transferred. The colors and animation associated with interface 724 facilitate an improved user experience for users of planning tool 700. The colors and animations provide the user with insight as to how resources are being transferred between assets of the central plant.

As shown in FIGS. 25-27, the user has the ability to delete symbols from workspace 1300 at any time. As shown in FIG. 25, the user right clicks on chilled water load 1331 using pointer 1402 and selects the “delete” option. In FIG. 26, a “confirm delete” dialog box 2602 appears, and the user selects the “yes” option to delete chilled water load 1331 from workspace 1300. FIG. 27 illustrates the absence of chilled water load 1300 along with all associated connections (i.e., connections 2107 and 2108).

As shown in FIG. 28, the user may attempt to save the central plant model by clicking the save button using mouse pointer 1402. However, after the save button is clicked, a “missed connections” dialog box 2904 may be generated as shown in FIG. 29. Missed connections dialog box 2904 can include a list of any connections missing from the central plant model that are required according to the symbols the user has added to workspace 1300 and the set of rules associated with planning tool 700. The user may select the continue button in order to return to the model specify any missing connections. In some embodiments, planning tool 700 is configured to generate and display a “view missed connections” button 1602 on interface 724 as shown in FIG. 30. The user may select button 1602 at any time to view a list of missing requirements associated with the central plant model.

As illustrated in FIG. 30, the user has added two new chilled water loads (chilled water load 1332 and chilled water load 1333) to workspace 1300. The user has also formed a connection 2109 between chiller plant 1322 and chilled water load 1332 as well as a connection 2110 between chiller tower plant 1323 and chilled water load 1333.

Also illustrated in FIG. 30 are warning icons located above tower plant 1321 (warning icon 3001), chiller plant 1322 (warning icon 3002), and chiller tower plant 1323 (warning icon 3003). These warning icons can signify to that the user need to specify equipment contained within the subplants. The warning icons can be generated according to the set of rules used by planning tool 700 as described in more detail below.

As illustrated in FIG. 31, the user may right click on tower plant 1321 using pointer 1402 and select the “add/view equipment” option. FIG. 32 shows a new workspace 3200 that is associated with tower plant 1321 and appears after the user clicks the add/view equipment option. As shown, symbol palette 1200 now has an equipment tab 1260 that contains symbols representing any sub-equipment or devices that can be contained within tower plant 1321. The symbols that appear in equipment tab 1260 may be generated according to the set of rules associated with planning tool 700 (e.g., certain equipment can be contained within certain subplants). In this case, the user adds a cooling tower symbol 3261 to workspace 3200 using the cooling tower symbol 1261 from equipment tab 1260. Moreover, as illustrated in FIG. 33, the user may right click on cooling tower symbol 3261 using pointer 1402 and select the “properties” option. After clicking the properties option, a property panel dialog box 3402 may appear as shown in FIG. 34. Property panel dialog box 3402 can be used to give cooling tower symbol 3261 a customized name, specify a capacity of the cooling tower, and/or specify a minimum turndown for the cooling tower. The three fields shown in property panel 3402 may be generated according to the set of rules. For example, the property panel dialog box for a different type of equipment (e.g., hot water generator) may contain different fields according to the set of rules. After the user has added cooling tower symbol 3261 and specified the associated properties, the user may save their work and interface 724 may display an “equipment saved successfully” message 3502 and a “properties saved successfully” message 3504 as shown in FIG. 35.

As illustrated in FIG. 36, warning icon 3001 associated with tower plant 1321 has now been replaced with a number “1” indicating that one piece of equipment (i.e., cooling tower 3261) has been associated with tower plant 1321. Also shown in FIG. 26, the user may right click on chiller plant symbol 1322 and selects the add/view equipment option using pointer 1402. As shown in FIG. 37, the user adds a chiller symbol 3762 to a workspace 3700 associated with chiller plant 1322 by using the chiller symbol 1262 from equipment tab 1260. The user may specify and save any properties associated with chiller 3762. As shown in FIG. 38, warning icon 3002 associated with chiller plant 1322 may also been replaced with a number 1.

As shown in FIGS. 39-40, the user may right click on chiller tower plant 1323, select the properties option, and customize the symbol name using a dialog box 4002. Any symbols displayed on interface 724 may be renamed according to user preferences in a similar manner. In FIG. 41, the user right clicks on chiller tower plant symbol 1323 using pointer 1402 and selects the add/view equipment option. In FIG. 42, the user adds a cooling tower symbol 4263 and a chiller symbol 4262 to a workspace 4200 associated with chiller tower plant 1323 using cooling tower symbol 1261 and chiller symbol 1262, respectively, from equipment tab 1260. After the user saves these changes, warning icon 3003 associated with chiller tower plant 1323 has been replaced with the number 2 as illustrated in FIG. 43.

As illustrated in FIG. 44, the central plant model created in workspace 1300 contains no warning icons after equipment has been associated with each of subplants 1321, 1322, and 1323. When the user clicks the save button, an alert 4412 can be displayed to indicate that the central plant model has been saved successfully. Missed connections dialog box 2904 no longer appears since the user has created a valid central plant model that satisfies the set of rules. In some embodiments, planning tool 700 provides users with the ability to toggle between a high level view of a central plant model (e.g., sources 410, subplants 420, storage 430, and sinks 440 on workspace 1300) and a low level view (e.g., equipment contained within all subplants).

As mentioned above, planning tool 700 can include a set of rules that governs valid central plant models created using interface 724 of planning tool 700. There may be different rules associated with each of sources 410, subplants 420, storage 430, and sinks 440 that are available to the user via symbol palette 1200. In addition, there may be different rules associated with the different types of equipment available to the user via symbol palette 1200. These rules work to ensure that users of planning tool 700 are creating feasible central plant models. This can lead to more accurate simulation results as well as more efficient design of an actual central plant.

Referring now to FIGS. 45A-45B, a table 4500 showing an example set of rules associated with planning tool 700 is shown. Various rules are shown for sources 410 (category “supplier”), subplants 420 (category “plant”), storage 430 (category “storage”), and sinks 440 (category “load”). Column 4501 shows a variety of components (e.g., sources 410, subplants 420, storage 430, and sinks 440) that can be used to create a central plant model. For example, as shown in column 4502, subplants available to users of planning tool 700 can include a chiller plant, a chiller tower plant (with wet bulb adjust), a tower plant (with wet bulb adjust), an air-cooled chiller plant with wet bulb adjust, a water-side economizer plant, a steam absorption chiller plant, a steam driven chiller tower plant, a heat recovery chiller plant, a steam heat exchanger plant, a dump heat exchanger plant, a hot water generator plant, and a boiler plant. Column 4502 indicates a type of component. For example, the components shown in column 4501 may be represented by symbols in symbol palette 1200, and they type of component shown in column 4502 may specify which tab the symbol can be found under (e.g., supplier tab 1210, etc.).

Table 4500 is also shown to include a column 4503 that indicates equipment that can be contained within certain components in column 4501. The equipment shown in column 4503 may be contained in equipment tab 1260 of symbol palette 1200, for example. Columns 4504, 4505, 4506, and 4507 show valid input components, whether the input components are required or optional, and an input resource type and color. Similarly, columns 4508 and 4509 show valid required and optional output components.

As an example, for a chiller plant (third row of table 4500), the user may be required to specify an electricity supplier input (e.g., connection 2104). The user may also be required to specify a chilled water load (e.g., connection 2107) while also having the option to specify a chilled water thermal storage tank output. The user may also be required to specify a chiller (e.g., chiller 3762) associated with the chiller plant. It will be appreciated that the rules shown in table 4500 are examples and variations thereof are contemplated within the scope of the present disclosure.

Configuration of Exemplary Embodiments

The construction and arrangement of the systems and methods as shown in the various exemplary embodiments are illustrative only. Although only a few embodiments have been described in detail in this disclosure, many modifications are possible (e.g., variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations, etc.). For example, the position of elements can be reversed or otherwise varied and the nature or number of discrete elements or positions can be altered or varied. Accordingly, all such modifications are intended to be included within the scope of the present disclosure. The order or sequence of any process or method steps can be varied or re-sequenced according to alternative embodiments. Other substitutions, modifications, changes, and omissions can be made in the design, operating conditions and arrangement of the exemplary embodiments without departing from the scope of the present disclosure.

The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure can be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system. Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.

Although the figures show a specific order of method steps, the order of the steps may differ from what is depicted. Also two or more steps can be performed concurrently or with partial concurrence. Such variation will depend on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the disclosure. Likewise, software implementations could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various connection steps, processing steps, comparison steps and decision steps. 

What is claimed is:
 1. A system comprising one or more computer-readable storage media having instructions stored thereon that, when executed by one or more processors, cause the one or more processors to: provide a user interface comprising a workspace with selectable symbols representing multiple devices of building equipment; evaluate a user input defining a connection between at least two of the selectable symbols on the workspace according to a set of rules to determine whether the connection is valid or invalid; prevent the user from making the connection in response to determining that the connection is invalid; generate a valid model of a system comprising the multiple devices of building equipment in response to determining that the connection is valid; execute a model-based control process or simulation using the valid model to generate control decisions or design decisions for the multiple devices of building equipment; and operate or design the multiple devices of building equipment in accordance with the control decisions or the design decisions.
 2. The system of claim 1, wherein the multiple devices of building equipment represented by the selectable symbols comprise at least two of a resource supplier, a subplant, an energy load, and a resource storage device.
 3. The system of claim 1, wherein: the user input defines the connection between a first connection point of a first selectable symbol of the selectable symbols and a second connection point of a second selectable symbol of the selectable symbols; and evaluating the user input according to the set of rules to determine whether the connection is valid or invalid comprises determining whether the first connection point and the second connection point are associated with different types of resources.
 4. The system of claim 1, wherein evaluating the user input according to the set of rules to determine whether the connection is valid or invalid comprises: identifying a first type of resource provided as an output by a first device of the building equipment represented by a first selectable symbol of the selectable symbols connected by the connection; identifying a second type of resource received as an input by a second device of the building equipment represented by a second selectable symbol of the selectable symbols connected by the connection; and determining whether the first type of resource is different from the second type of resource.
 5. The system of claim 1, wherein the instructions cause the one or more processors to: identify a type of resource transferred between the multiple devices of building equipment represented by the selectable symbols connected by the connection; select a color for the connection based on the type of resource; and present the connection as a colored object having the selected color.
 6. The system of claim 1, wherein the instructions cause the one or more processors to present the connection as an animated line that indicates transfer of a resource between a first device of the building equipment represented by a first selectable symbol of the selectable symbols connected by the connection and a second device of the building equipment represented by a second selectable symbol of the selectable symbols connected by the connection.
 7. The system of claim 1, wherein the set of rules indicate required connections between the selectable symbols and the instructions cause the one or more processors to: determine whether all of the required connections between the selectable symbols have been defined; and present an indication of missing connections between the selectable symbols via the user interface in response to determining that one or more of the required connections have not been defined.
 8. The system of claim 1, wherein at least one of the selectable symbols represents a subplant comprising multiple devices of the building equipment and the set of rules define required equipment within the subplant, wherein the instructions cause the one or more processors to: determine whether all of the required equipment within the subplant have been specified; and present an indication of missing equipment within the subplant via the user interface in response to determining that one or more of the required equipment within the subplant have not been specified.
 9. The system of claim 1, wherein: the set of rules define valid relationships between the multiple devices of building equipment; and evaluating the user input according to the set of rules to determine whether the connection is valid or invalid comprises determining whether the connection indicates a valid relationship between the multiple devices of building equipment according to the set of rules.
 10. The system of claim 1, wherein executing the model-based control process or simulation using the valid model comprises using the connection to define a constraint on the model-based control process or simulation.
 11. A method comprising: providing a user interface comprising a workspace with selectable symbols representing multiple devices of building equipment; evaluating a user input defining a connection between at least two of the selectable symbols on the workspace according to a set of rules to determine whether the connection is valid or invalid; preventing the user from making the connection in response to determining that the connection is invalid; generating a valid model of a system comprising the multiple devices of building equipment in response to determining that the connection is valid; executing a model-based control process or simulation using the valid model to generate control decisions or design decisions for the multiple devices of building equipment; and operating or design the multiple devices of building equipment in accordance with the control decisions or the design decisions.
 12. The method of claim 11, wherein the multiple devices of building equipment represented by the selectable symbols comprise at least two of a resource supplier, a subplant, an energy load, and a resource storage device.
 13. The method of claim 11, wherein: the user input defines the connection between a first connection point of a first selectable symbol of the selectable symbols and a second connection point of a second selectable symbol of the selectable symbols; and evaluating the user input according to the set of rules to determine whether the connection is valid or invalid comprises determining whether the first connection point and the second connection point are associated with different types of resources.
 14. The method of claim 11, wherein evaluating the user input according to the set of rules to determine whether the connection is valid or invalid comprises: identifying a first type of resource provided as an output by a first device of the building equipment represented by a first selectable symbol of the selectable symbols connected by the connection; identifying a second type of resource received as an input by a second device of the building equipment represented by a second selectable symbol of the selectable symbols connected by the connection; and determining whether the first type of resource is different from the second type of resource.
 15. The method of claim 11, comprising: identifying a type of resource transferred between the multiple devices of building equipment represented by the selectable symbols connected by the connection; selecting a color for the connection based on the type of resource; and presenting the connection as a colored object having the selected color.
 16. The method of claim 11, comprising presenting the connection as an animated line that indicates transfer of a resource between a first device of the building equipment represented by a first selectable symbol of the selectable symbols connected by the connection and a second device of the building equipment represented by a second selectable symbol of the selectable symbols connected by the connection.
 17. The method of claim 11, wherein the set of rules indicate required connections between the selectable symbols, the method comprising: determining whether all of the required connections between the selectable symbols have been defined; and presenting an indication of missing connections between the selectable symbols via the user interface in response to determining that one or more of the required connections have not been defined.
 18. The method of claim 11, wherein at least one of the selectable symbols represents a subplant comprising multiple devices of the building equipment and the set of rules define required equipment within the subplant, the method comprising: determining whether all of the required equipment within the subplant have been specified; and presenting an indication of missing equipment within the subplant via the user interface in response to determining that one or more of the required equipment within the subplant have not been specified.
 19. The method of claim 11, wherein: the set of rules define valid relationships between the multiple devices of building equipment; and evaluating the user input according to the set of rules to determine whether the connection is valid or invalid comprises determining whether the connection indicates a valid relationship between the multiple devices of building equipment according to the set of rules.
 20. The method of claim 11, wherein executing the model-based control process or simulation using the valid model comprises using the connection to define a constraint on the model-based control process or simulation. 